You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@impala.apache.org by ta...@apache.org on 2019/12/17 17:00:43 UTC
[impala] 01/04: [DOCS] Clarification on HADOOP-15720 in
impala_known_issues.xml
This is an automated email from the ASF dual-hosted git repository.
tarmstrong pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/impala.git
commit cd7454be660a8b6895f440c3eab8a707587ad2c5
Author: Alex Rodoni <ar...@cloudera.com>
AuthorDate: Fri Dec 13 12:52:34 2019 -0800
[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 <im...@cloudera.com>
Reviewed-by: Robbie Zhang <rz...@cloudera.com>
Reviewed-by: Joe McDonnell <jo...@cloudera.com>
---
docs/topics/impala_known_issues.xml | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
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 @@ explain SELECT 1 FROM alltypestiny a1
<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 <filename> at backend <hostname:port> failed to finish before the <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>