[
https://issues.apache.org/jira/browse/IMPALA-14073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954929#comment-17954929
]
Csaba Ringhofer commented on IMPALA-14073:
------------------------------------------
See an issue in this test, probably it is the same (I can create a new ticket
if it is a different issue)
{code}
custom_cluster/test_concurrent_ddls.py:78: in
test_local_catalog_ddls_with_invalidate_metadata
self._run_ddls_with_invalidation(unique_database, sync_ddl=False)
custom_cluster/test_concurrent_ddls.py:169: in _run_ddls_with_invalidation
worker[i].get(timeout=100)
Impala-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 3d42af0eb6939e9e:a2f4e11200000000 failed:
E AnalysisException: Table already exists:
test_local_catalog_ddls_with_invalidate_metadata_e78f2324.test_3_part
E
E
E assert <bound method type.is_acceptable_error of <class
'test_concurrent_ddls.TestConcurrentDdls'>>('Query
3d42af0eb6939e9e:a2f4e11200000000 failed:\nAnalysisException: Table already
exists:
test_local_catalog_ddls_with_invalidate_metadata_e78f2324.test_3_part\n\n',
False)
E + where <bound method type.is_acceptable_error of <class
'test_concurrent_ddls.TestConcurrentDdls'>> =
<test_concurrent_ddls.TestConcurrentDdls object at
0x7f76204f3ed0>.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]
