You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@impala.apache.org by "Adriano (Jira)" <ji...@apache.org> on 2021/02/12 09:41:00 UTC

[jira] [Created] (IMPALA-10502) delayed 'Invalidated objects in cache' cause 'Table already exists'

Adriano created IMPALA-10502:
--------------------------------

             Summary: delayed 'Invalidated objects in cache' cause 'Table already exists'
                 Key: IMPALA-10502
                 URL: https://issues.apache.org/jira/browse/IMPALA-10502
             Project: IMPALA
          Issue Type: Bug
          Components: Catalog, Clients, Frontend
    Affects Versions: Impala 3.4.0
            Reporter: Adriano


In fast paced environment where the interval between the step 1 and 2 is # < 100ms (a simplified pipeline looks like):

0- catalog 'on demand' in use and disableHmsSync (enabled or disabled: no difference)
1- open session to coord A -> DROP TABLE X -> close session
2- open session to coord A -> CREATE TABLE X-> close session

Results: the step -2- can fail with table already exist.

During the internal investigation was discovered that IMPALA-9913 will regress the issue in almost all scenarios.
However considering that the investigation are internally ongoing it is nice to have the event tracked also here.
Once we are sure that IMPALA-9913 fix these events we can close this as duplicate, in alternative carry on the investigation.



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