You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "Joe McDonnell (Jira)" <ji...@apache.org> on 2019/11/18 23:13:00 UTC

[jira] [Created] (IMPALA-9168) TestConcurrentDdls flaky on s3 (Count not resolve table reference)

Joe McDonnell created IMPALA-9168:
-------------------------------------

             Summary: TestConcurrentDdls flaky on s3 (Count not resolve table reference)
                 Key: IMPALA-9168
                 URL: https://issues.apache.org/jira/browse/IMPALA-9168
             Project: IMPALA
          Issue Type: Bug
          Components: Frontend
    Affects Versions: Impala 3.4.0
            Reporter: Joe McDonnell
            Assignee: Quanlong Huang


There have been a couple failures for TestConcurrentDdls on s3. They are on different tests but have a similar symptom.

TestConcurrentDdls.test_mixed_catalog_ddls_with_invalidate_metadata sees:
{noformat}
custom_cluster/test_concurrent_ddls.py:59: in test_mixed_catalog_ddls_with_invalidate_metadata
    self._run_ddls_with_invalidation(unique_database, sync_ddl=False)
custom_cluster/test_concurrent_ddls.py:136: in _run_ddls_with_invalidation
    for i in pool.imap_unordered(run_ddls, xrange(1, NUM_ITERS + 1)):
/usr/lib64/python2.7/multiprocessing/pool.py:655: in next
    raise value
E   AssertionError: ImpalaBeeswaxException:
E      INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E      MESSAGE: AnalysisException: Could not resolve table reference: 'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_10_part'
E     
E   assert <bound method type.is_acceptable_error of <class 'test_concurrent_ddls.TestConcurrentDdls'>>("ImpalaBeeswaxException:\n INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>\n MESSAGE: AnalysisException: Could not resolve table reference: 'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_10_part'\n", False)
E    +  where <bound method type.is_acceptable_error of <class 'test_concurrent_ddls.TestConcurrentDdls'>> = TestConcurrentDdls.is_acceptable_error
E    +  and   "ImpalaBeeswaxException:\n INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>\n MESSAGE: AnalysisException: Could not resolve table reference: 'test_mixed_catalog_ddls_with_invalidate_metadata_8d71c4db.test_10_part'\n" = str(ImpalaBeeswaxException()){noformat}
TestConcurrentDdls.test_local_catalog_ddls_with_invalidate_metadata_sync_ddl sees:
{noformat}
custom_cluster/test_concurrent_ddls.py:83: in test_local_catalog_ddls_with_invalidate_metadata_sync_ddl
    self._run_ddls_with_invalidation(unique_database, sync_ddl=True)
custom_cluster/test_concurrent_ddls.py:136: in _run_ddls_with_invalidation
    for i in pool.imap_unordered(run_ddls, xrange(1, NUM_ITERS + 1)):
/usr/lib64/python2.7/multiprocessing/pool.py:655: in next
    raise value
E   AssertionError: ImpalaBeeswaxException:
E      INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>
E      MESSAGE: AnalysisException: Table does not exist: test_local_catalog_ddls_with_invalidate_metadata_sync_ddl_b87f02d6.test_15
E     
E   assert <bound method type.is_acceptable_error of <class 'test_concurrent_ddls.TestConcurrentDdls'>>("ImpalaBeeswaxException:\n INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>\n MESSAGE: AnalysisException: Table does not exist: test_local_catalog_ddls_with_invalidate_metadata_sync_ddl_b87f02d6.test_15\n", True)
E    +  where <bound method type.is_acceptable_error of <class 'test_concurrent_ddls.TestConcurrentDdls'>> = TestConcurrentDdls.is_acceptable_error
E    +  and   "ImpalaBeeswaxException:\n INNER EXCEPTION: <class 'beeswaxd.ttypes.BeeswaxException'>\n MESSAGE: AnalysisException: Table does not exist: test_local_catalog_ddls_with_invalidate_metadata_sync_ddl_b87f02d6.test_15\n" = str(ImpalaBeeswaxException()){noformat}
These are the only two occurrences so far, and both are on s3. This test came in with "IMPALA-7506: support global INVALIDATE METADATA in local catalog mode"



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org