[
https://issues.apache.org/jira/browse/IMPALA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18005215#comment-18005215
]
Riza Suminto commented on IMPALA-14073:
---------------------------------------
This test has been flaky since new test cases added by IMPALA-13631. After
that, CatalogD does not hold catalogVersion when invoking HMS rename RPC.
concurrent global Invalidate Metadata from other test threads can fail RENAME
ddl.
{code:java}
diff --git a/tests/custom_cluster/test_concurrent_ddls.py
b/tests/custom_cluster/test_concurrent_ddls.py
index 1eef3b7..ef04ae0 100644
--- a/tests/custom_cluster/test_concurrent_ddls.py
+++ b/tests/custom_cluster/test_concurrent_ddls.py
@@ -110,6 +110,10 @@ class TestConcurrentDdls(CustomClusterTestSuite):
# Below queries could fail if running with invalidate metadata
concurrently
"alter table %s_part add partition (j=1)" % tbl_name,
"alter table %s_part add partition (j=2)" % tbl_name,
+ "alter table {0} rename to {0}_2".format(tbl_name),
+ "alter table {0}_part rename to {0}_part2".format(tbl_name),
+ "alter table {0}_2 rename to {0}".format(tbl_name),
+ "alter table {0}_part2 rename to {0}_part".format(tbl_name),
"invalidate metadata %s_part" % tbl_name,
"refresh %s" % tbl_name,
"refresh %s_part" % tbl_name, {code}
> test_local_catalog_ddls_with_invalidate_metadata_sync_ddl is flaky after
> IMPALA-13631
> -------------------------------------------------------------------------------------
>
> Key: IMPALA-14073
> URL: https://issues.apache.org/jira/browse/IMPALA-14073
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog, Test
> Affects Versions: Impala 5.0.0
> Reporter: Riza Suminto
> Priority: Major
> Labels: broken-build
>
> IMPALA-13631 change alterTableOrViewRename to not hold catalog version lock
> while making HMS RPC.
> It adds back-and-forth ALTER TABLE RENAME testcase into
> test_local_catalog_ddls_with_invalidate_metadata_sync_ddl, which make it
> flaky for causing DDL occasionally not finding the target table after
> concurrent RENAME-INVALIDATE-REFRESH.
> We need to understand what happen and how to make the test deterministic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]