[
https://issues.apache.org/jira/browse/IMPALA-13143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Quanlong Huang updated IMPALA-13143:
------------------------------------
Fix Version/s: Impala 4.4.1
> TestCatalogdHA.test_catalogd_failover_with_sync_ddl times out expecting query
> failure
> -------------------------------------------------------------------------------------
>
> Key: IMPALA-13143
> URL: https://issues.apache.org/jira/browse/IMPALA-13143
> Project: IMPALA
> Issue Type: Bug
> Components: Backend
> Affects Versions: Impala 4.5.0
> Reporter: Joe McDonnell
> Assignee: Wenzhe Zhou
> Priority: Critical
> Labels: broken-build, flaky
> Fix For: Impala 4.5.0, Impala 4.4.1
>
>
> The new TestCatalogdHA.test_catalogd_failover_with_sync_ddl test is failing
> intermittently with:
> {noformat}
> custom_cluster/test_catalogd_ha.py:472: in
> test_catalogd_failover_with_sync_ddl
> self.wait_for_state(handle, QueryState.EXCEPTION, 30, client=client)
> common/impala_test_suite.py:1216: in wait_for_state
> self.wait_for_any_state(handle, [expected_state], timeout, client)
> common/impala_test_suite.py:1234: in wait_for_any_state
> raise Timeout(timeout_msg)
> E Timeout: query '9d49ab6360f6cbc5:4826a79600000000' did not reach one of
> the expected states [5], last known state 4{noformat}
> This means the query succeeded even though we expected it to fail. This is
> currently limited to s3 jobs. In a different test, we saw issues because s3
> is slower (see IMPALA-12616).
> This test was introduced by IMPALA-13134:
> https://github.com/apache/impala/commit/70b7b6a78d49c30933d79e0a1c2a725f7e0a3e50
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
