[
https://issues.apache.org/jira/browse/IMPALA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18004863#comment-18004863
]
Quanlong Huang commented on IMPALA-14073:
-----------------------------------------
Saw a similar failure:
https://jenkins.impala.io/job/ubuntu-20.04-from-scratch/6039/testReport/junit/custom_cluster.test_concurrent_ddls/TestConcurrentDdls/test_ddls_with_invalidate_metadata_sync_ddl/
{code}
custom_cluster/test_concurrent_ddls.py:57: in
test_ddls_with_invalidate_metadata_sync_ddl
self._run_ddls_with_invalidation(unique_database, sync_ddl=True)
custom_cluster/test_concurrent_ddls.py:179: in _run_ddls_with_invalidation
worker[i].get(timeout=100)
../toolchain/toolchain-packages-gcc10.4.0/python-2.7.16/lib/python2.7/multiprocessing/pool.py:572:
in get
raise self._value
E AssertionError: Query c74c1222c84c1f3b:8b68810a00000000 failed:
E AnalysisException: Table already exists:
test_ddls_with_invalidate_metadata_sync_ddl_f41e97e6.test_10_part
E
E
E assert <bound method type.is_acceptable_error of <class
'test_concurrent_ddls.TestConcurrentDdls'>>('Query
c74c1222c84c1f3b:8b68810a00000000 failed:\nAnalysisException: Table already
exists: test_ddls_with_invalidate_metadata_sync_ddl_f41e97e6.test_10_part\n\n',
True)
E + where <bound method type.is_acceptable_error of <class
'test_concurrent_ddls.TestConcurrentDdls'>> =
<test_concurrent_ddls.TestConcurrentDdls object at
0x7f2b28c835d0>.is_acceptable_error{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]
