Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-10502

delayed 'Invalidated objects in cache' cause 'Table already exists'

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Open
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: Impala 3.4.0
    • Fix Version/s: None
    • Component/s: Catalog, Clients, Frontend
    • Labels:
      None
    • Epic Color:
      ghx-label-13

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              vihangk1 Vihang Karajgaonkar
              Reporter:
              adrenas Adriano
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated: