Surya Hebbar created IMPALA-13995:
-------------------------------------

             Summary: 
TestConcurrentDdls.test_mixed_catalog_ddls_with_invalidate_metadata tests are 
flaky
                 Key: IMPALA-13995
                 URL: https://issues.apache.org/jira/browse/IMPALA-13995
             Project: IMPALA
          Issue Type: Bug
            Reporter: Surya Hebbar


TestConcurrentDdls.test_mixed_catalog_ddls_with_invalidate_metadata tests are 
flaky across core-s3, arm and jdk17 builds

The other possibly related failing tests are
test_mixed_catalog_ddls_with_invalidate_metadata
test_local_catalog_ddls_with_invalidate_metadata
test_ddls_with_invalidate_metadata

Error Message -
{code}
AssertionError: Query 4b4505742c35a8b1:ec3e9eda00000000 failed:   
ImpalaRuntimeException: Table/view rename succeeded in the Hive Metastore, but 
failed in Impala's Catalog Server. Running 'invalidate metadata <tbl>' on the 
old table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part2' and 
the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.       assert <bound method type.is_acceptable_error of <class 
'test_concurrent_ddls.TestConcurrentDdls'>>("Query 
4b4505742c35a8b1:ec3e9eda00000000 failed:\nImpalaRuntimeException: Table/view 
rename succeeded in the Hive Meta...d the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.\n\n", False)  +  where <bound method type.is_acceptable_error 
of <class 'test_concurrent_ddls.TestConcurrentDdls'>> = 
TestConcurrentDdls.is_acceptable_error  +  and   "Query 
4b4505742c35a8b1:ec3e9eda00000000 failed:\nImpalaRuntimeException: Table/view 
rename succeeded in the Hive Meta...d the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.\n\n" = str(ImpalaBeeswaxException())
{code}

Stacktrace
{code}
custom_cluster/test_concurrent_ddls.py:60: in 
test_mixed_catalog_ddls_with_invalidate_metadata
    self._run_ddls_with_invalidation(unique_database, sync_ddl=False)
custom_cluster/test_concurrent_ddls.py:154: in _run_ddls_with_invalidation
    worker[i].get(timeout=100)
/data/jenkins/workspace/impala-asf-master-core-asan-arm/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 4b4505742c35a8b1:ec3e9eda00000000 failed:
E     ImpalaRuntimeException: Table/view rename succeeded in the Hive 
Metastore, but failed in Impala's Catalog Server. Running 'invalidate metadata 
<tbl>' on the old table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part2' and 
the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.
E     
E     
E   assert <bound method type.is_acceptable_error of <class 
'test_concurrent_ddls.TestConcurrentDdls'>>("Query 
4b4505742c35a8b1:ec3e9eda00000000 failed:\nImpalaRuntimeException: Table/view 
rename succeeded in the Hive Meta...d the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.\n\n", False)
E    +  where <bound method type.is_acceptable_error of <class 
'test_concurrent_ddls.TestConcurrentDdls'>> = 
TestConcurrentDdls.is_acceptable_error
E    +  and   "Query 4b4505742c35a8b1:ec3e9eda00000000 
failed:\nImpalaRuntimeException: Table/view rename succeeded in the Hive 
Meta...d the new table name 
'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_16_part' may 
fix the problem.\n\n" = str(ImpalaBeeswaxException()){code}
 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to