Andrew Sherman created IMPALA-8183:
--------------------------------------
Summary: TestRPCTimeout.test_reportexecstatus_retry times out
Key: IMPALA-8183
URL: https://issues.apache.org/jira/browse/IMPALA-8183
Project: IMPALA
Issue Type: Bug
Reporter: Andrew Sherman
There are 2 forms of failure, where the test itself times out, and where the
whole test run times out, suspiciously just after running
test_reportexecstatus_retry
{quote}
Error Message
Failed: Timeout >7200s
Stacktrace
custom_cluster/test_rpc_timeout.py:143: in test_reportexecstatus_retry
self.execute_query_verify_metrics(self.TEST_QUERY, None, 10)
custom_cluster/test_rpc_timeout.py:45: in execute_query_verify_metrics
self.execute_query(query, query_options)
common/impala_test_suite.py:601: in wrapper
return function(*args, **kwargs)
common/impala_test_suite.py:632: in execute_query
return self.__execute_query(self.client, query, query_options)
common/impala_test_suite.py:699: in __execute_query
return impalad_client.execute(query, user=user)
common/impala_connection.py:174: in execute
return self.__beeswax_client.execute(sql_stmt, user=user)
beeswax/impala_beeswax.py:183: in execute
handle = self.__execute_query(query_string.strip(), user=user)
beeswax/impala_beeswax.py:360: in __execute_query
self.wait_for_finished(handle)
beeswax/impala_beeswax.py:384: in wait_for_finished
time.sleep(0.05)
E Failed: Timeout >7200s
{quote}
{quote}
Test run timed out. This probably happened due to a hung thread which can be
confirmed by looking at the stacktrace of running impalad processes at
/data/jenkins/workspace/xxx/repos/Impala/logs/timeout_stacktrace
{quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
