commit cd7454be660a8b6895f440c3eab8a707587ad2c5
author Alex Rodoni <arodoni@cloudera.com> Fri Dec 13 12:52:34 2019 -0800
committer Alex Rodoni <arodoni@cloudera.com> Mon Dec 16 18:53:40 2019 +0000
tree d1ef454603c0ac3f28522322d29acb307eea6632
parent f2f348c0f93208a0f34c33b6a4dc82f4d9d4b290

[DOCS] Clarification on HADOOP-15720 in impala_known_issues.xml

Change-Id: I724085ee63005cb2ce68a4532e6cf315d4799e7a
Reviewed-on: http://gerrit.cloudera.org:8080/14906
Tested-by: Impala Public Jenkins <impala-public-jenkins@cloudera.com>
Reviewed-by: Robbie Zhang <rzhang@cloudera.com>
Reviewed-by: Joe McDonnell <joemcdonnell@cloudera.com>

docs/topics/impala_known_issues.xml

diff --git a/docs/topics/impala_known_issues.xml b/docs/topics/impala_known_issues.xml
index 6b0331a..7ad7604 100644
--- a/docs/topics/impala_known_issues.xml
+++ b/docs/topics/impala_known_issues.xml
@@ -652,15 +652,15 @@
       <title>Queries Stuck on Failed HDFS Calls and not Timing out</title>
 
       <conbody>
-
-        <p>
-          If the following error appears multiple times in a short duration while running a
-          query, it would mean that the connection between the <codeph>impalad</codeph> and the
-          HDFS NameNode is in a bad state and hence the <codeph>impalad</codeph> would have to
-          be restarted:
-        </p>
+        <p> In Impala 3.2 and higher, if the following error appears multiple
+          times in a short duration while running a query, it would mean that
+          the connection between the <codeph>impalad</codeph> and the HDFS
+          NameNode is in a bad state and hence the <codeph>impalad</codeph>
+          would have to be restarted: </p>
 
 <codeblock>"hdfsOpenFile() for &lt;filename> at backend &lt;hostname:port> failed to finish before the &lt;hdfs_operation_timeout_sec> second timeout " </codeblock>
+        <p>In Impala 3.1 and lower, the same issue would cause Impala to wait for
+          a long time or hang without showing the above error message.</p>
 
         <p>
           <b>Apache Issue:</b>