You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2024/06/07 16:42:00 UTC

[jira] [Created] (IMPALA-13143) TestCatalogdHA.test_catalogd_failover_with_sync_ddl times out expecting query failure

Joe McDonnell created IMPALA-13143:
--------------------------------------

             Summary: 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


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)