[jira] [Closed] (IMPALA-13765) Custom Cluster Test Failure in wait_for_wm_init_complete

["Jason Fehr (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-13765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Fehr closed IMPALA-13765.
-------------------------------
    Resolution: Duplicate

> Custom Cluster Test Failure in wait_for_wm_init_complete
> --------------------------------------------------------
>
>                 Key: IMPALA-13765
>                 URL: https://issues.apache.org/jira/browse/IMPALA-13765
>             Project: IMPALA
>          Issue Type: Bug
>            Reporter: Jason Fehr
>            Assignee: Jason Fehr
>            Priority: Major
>
> Custom cluster tests that call CustomClusterTestSuite.wait_for_wm_init_complete can timeout during this function call.  The specific stack trace is:
> {noformat}
> custom_cluster/test_query_log.py:56: in setup_method
>     self.wait_for_wm_init_complete()
> common/custom_cluster_test_suite.py:419: in wait_for_wm_init_complete
>     r'assembled\. Catalog version: (\d+)', timeout_s)
> common/impala_test_suite.py:1561: in assert_log_contains_multiline
>     "contents matching the regex '{}'".format(line_regex)
> E   AssertionError: did not find any logfile contents matching the regex 'Completed workload management initialization.*?A catalog update with \d+ entries is assembled\. Catalog version: (\d+)'
> {noformat}
> Investigating one of these test failures in the TestQueryLogTableAll.test_sql_injection_attempts test showed the time from catalogd startup to test failure was less than 10 seconds despite this test using the default timeout_s of 60 seconds.
> Need to determine why the full timeout is not being waited.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)