[IMPALA-10352] test_error_query_state failed after timeout is reached

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: Impala 4.0.0
• Labels: broken-build flaky
• Epic Color: ghx-label-2
• Assignee: Quanlong Huang
• Reporter: Fang-Yu Rao
• Created: 24/Nov/20 01:09
• Updated: 24/Nov/20 01:18
• Resolved: 24/Nov/20 01:18

Description

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).

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

In the corresponding log of impalad, we have the following entry, we found the following entry corresponding to the executed query.

I1122 17:58:34.133029 10914 coordinator.cc:148] a849da33d0fd09b9:eb891b0e00000000] Exec() query_id=a849da33d0fd09b9:eb891b0e00000000 stmt=select * from functional.alltypes limit 10

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. Also let me know if you need other log files to debug the issue.

Issue Links

• duplicates: IMPALA-9833 query_test.test_observability.TestQueryStates.test_error_query_state is flaky