You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Jason Fehr (Jira)" <ji...@apache.org> on 2025/09/05 03:23:00 UTC
[jira] [Created] (IMPALA-14401) Deflake OTel Custom Cluster Test
Jason Fehr created IMPALA-14401:
-----------------------------------
Summary: Deflake OTel Custom Cluster Test
Key: IMPALA-14401
URL: https://issues.apache.org/jira/browse/IMPALA-14401
Project: IMPALA
Issue Type: Improvement
Affects Versions: Impala 5.0.0
Reporter: Jason Fehr
Assignee: Jason Fehr
In test_otel_trace.py, the test_ddl_createtable_fail has a potential to be flaky. In the test, the second coordinator that drops the database may run that DDL too quickly before the create database operation executed on the first coordinator propagates to the second coordinator.
In the test, first retrieve the number of databases from the "catalog.num-databases" metric:
{code:python}
num_dbs = self.cluster.get_first_impalad().service.get_metric_value("catalog.num-databases")
{code}
Then, before the drop database DDL, wait for the second coordinator's "catalog.num-databases" metric to increment by 1:
{code:python}
self.cluster.impalads[1].service.wait_for_metric_value("catalog.num-databases", num_dbs + 1, 60)
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)