[
https://issues.apache.org/jira/browse/IMPALA-10258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17274192#comment-17274192
]
Wenzhe Zhou commented on IMPALA-10258:
--------------------------------------
According to the back trace, the test was waiting for the query to reach state
"RUNNING" (QueryState = 3, see beeswax.thrift), but it was already at state
"EXCEPTION" (QueryState = 5). At that point in the test, the query shouldn't
have failed, since the query was not cancelled yet, so really not sure what
could have happened.
> TestQueryRetries.test_original_query_cancel is flaky
> -----------------------------------------------------
>
> Key: IMPALA-10258
> URL: https://issues.apache.org/jira/browse/IMPALA-10258
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Reporter: Quanlong Huang
> Assignee: Wenzhe Zhou
> Priority: Critical
> Labels: broken-build, flaky
> Fix For: Impala 4.0
>
>
> Saw this fails in a core-s3-data-cache build:
> custom_cluster.test_query_retries.TestQueryRetries.test_original_query_cancel
> {code:java}
> custom_cluster/test_query_retries.py:622: in test_original_query_cancel
> self.wait_for_state(handle, self.client.QUERY_STATES[state], 60)
> common/impala_test_suite.py:1053: in wait_for_state
> self.wait_for_any_state(handle, [expected_state], timeout, client)
> common/impala_test_suite.py:1070: in wait_for_any_state
> actual_state))
> E Timeout: query 494af68cdf3d8ecb:d3a3bf3600000000 did not reach one of the
> expected states [3], last known state 5{code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
