[
https://issues.apache.org/jira/browse/IMPALA-13536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17905479#comment-17905479
]
ASF subversion and git services commented on IMPALA-13536:
----------------------------------------------------------
Commit cb35dc87690b21a74acc7af599abd492db8cb52f in impala's branch
refs/heads/master from jasonmfehr
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=cb35dc876 ]
IMPALA-13536: Workload Management Tests Failing on Init Check
Most of the workload management tests verify that the workload
management process has successfully completed. Part of this
verification ensures a catalog update has propagated the workload
management changes to the coordinators by determining the catalog
version, from the catalogd logs, that contains the workload
management table changes and ensuring that version is in the
coordinator logs.
The test flakiness occurs when multiple catalogd versions are
combined into a later version. Specifically, tests were failing
because the coordinator logs were checked for catalog version X but
the actual version in the coordinator logs was X+1.
The fix for the test flakiness is to allow for the exepected catalog
version or any later version.
Change-Id: I9f20a149ab1f45ee3506f098f8594965a24a89d3
Reviewed-on: http://gerrit.cloudera.org:8080/22200
Reviewed-by: Jason Fehr <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Tests failing in TestWorkloadManagementInitWait on Ozone
> --------------------------------------------------------
>
> Key: IMPALA-13536
> URL: https://issues.apache.org/jira/browse/IMPALA-13536
> Project: IMPALA
> Issue Type: Bug
> Reporter: Daniel Becker
> Assignee: Jason Fehr
> Priority: Blocker
> Labels: broken-build
>
> Some of our tests failed in the test class
> test_workload_mgmt_init.py::TestWorkloadManagementInitWait.
> test_upgrade_1_0_0_to_1_1_0():
> {code:java}
> custom_cluster/test_workload_mgmt_init.py:222: in test_upgrade_1_0_0_to_1_1_0
> self.check_schema_version("1.1.0")
> custom_cluster/test_workload_mgmt_init.py:129: in check_schema_version
> self.assert_table_prop(tbl_name, "wm_schema_version", schema_version)
> custom_cluster/test_workload_mgmt_init.py:104: in assert_table_prop
> assert found, "did not find expected table prop '{}' with value '{}' on
> table " \
> E AssertionError: did not find expected table prop 'wm_schema_version' with
> value '1.1.0' on table 'sys.impala_query_log'
> E assert False
> {code}
> test_invalid_wm_schema_version_live_table_prop():
> {code:java}
> custom_cluster/test_workload_mgmt_init.py:375: in
> test_invalid_wm_schema_version_live_table_prop
> self._run_invalid_table_prop_test(self.QUERY_TBL_LIVE,
> "wm_schema_version")
> custom_cluster/test_workload_mgmt_init.py:325: in _run_invalid_table_prop_test
> "found on the '{}' property of table '{}'".format(prop_name, table))
> common/impala_test_suite.py:1351: in assert_catalogd_log_contains
> daemon, level, line_regex, expected_count, timeout_s, dry_run)
> common/impala_test_suite.py:1397: in assert_log_contains
> (expected_count, log_file_path, line_regex, found, line)
> E AssertionError: Expected 1 lines in file
> /data0/jenkins/workspace/impala-asf-master-core-ozone-erasure-coding/repos/Impala/logs/custom_cluster_tests/catalogd.impala-ec2-centos79-m6i-4xlarge-xldisk-126a.vpc.cloudera.com.jenkins.log.FATAL.20241107-042724.11427
> matching regex 'could not parse version string '' found on the
> 'wm_schema_version' property of table 'sys.impala_query_live'', but found 0
> lines. Last line was:
> E . Impalad exiting.
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
