[jira] [Created] (IMPALA-7093) Tables briefly appear to not exist after INVALIDATE METADATA or catalog restart

["Todd Lipcon (JIRA)" <ji...@apache.org>]

Todd Lipcon created IMPALA-7093:
-----------------------------------

             Summary: Tables briefly appear to not exist after INVALIDATE METADATA or catalog restart
                 Key: IMPALA-7093
                 URL: https://issues.apache.org/jira/browse/IMPALA-7093
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog
    Affects Versions: Impala 2.12.0, Impala 2.13.0
            Reporter: Todd Lipcon


I'm doing some stress testing of Impala 2.13 (recent snapshot build) and hit the following sequence:

{code}
 {"query": "SHOW TABLES in consistency_test", "type": "call", "id": 3}
{"type": "response", "id": 3, "results": [["t1"]]}
{"query": "INVALIDATE METADATA", "type": "call", "id": 7}
{"type": "response", "id": 7}
{"query": "DESCRIBE consistency_test.t1", "type": "call", "id": 9}
{"type": "response", "id": 9, "error": "AnalysisException: Could not resolve path: 'consistency_test.t1'\n"}
{code}

i.e. 'SHOW TABLES' shows that a table exists, but then shortly after an INVALIDATE METADATA, an attempt to describe a table indicates that the table does not exist. This is a single-threaded test case against a single impalad.

I also saw a similar behavior that issuing queries to an impalad shortly after a catalogd restart could transiently show tables not existing that in fact exist.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)