Fang-Yu Rao created IMPALA-10352:
------------------------------------
Summary: test_error_query_state failed after timeout is reached
Key: IMPALA-10352
URL: https://issues.apache.org/jira/browse/IMPALA-10352
Project: IMPALA
Issue Type: Bug
Affects Versions: Impala 4.0
Reporter: Fang-Yu Rao
Attachments: consoleFull_impala-cdpd-master-exhaustive-release.txt,
impalad_excerpted.INFO.zip
We found in an exhausitive build that {{test_error_query_state}} failed after
the specified timeout, which is 300 seconds as set up in IMPALA-9833 at
[https://github.com/apache/impala/blame/master/tests/query_test/test_observability.py#L805].
According to the attached console output, the test started to execute at
17:58:34 and failed at 18:03:34 (after 300 seconds have passed).
{noformat}
17:58:34
query_test/test_observability.py::TestQueryStates::test_error_query_state
18:03:34 [gw3] FAILED
query_test/test_observability.py::TestQueryStates::test_error_query_state
{noformat}
In the corresponding log of impalad, we have the following entry, we found the
following entry corresponding to the executed query.
{noformat}
I1122 17:58:34.133029 10914 coordinator.cc:148]
a849da33d0fd09b9:eb891b0e00000000] Exec()
query_id=a849da33d0fd09b9:eb891b0e00000000 stmt=select * from
functional.alltypes limit 10
{noformat}
Using the query id ({{a849da33d0fd09b9:eb891b0e00000000}}), I excerpted the log
entries between the time this query was registered and this query was deleted
and then attached those log entries.
[~tarmstrong] and [~stigahuang] reviewed the patch recently. Probably you could
provide some insight into it. Assigned the JIRA to Quanlong for now but feel
free to re-assign it as you see appropriate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
