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

Share metastoreHmsDDL lock b/w CatalogOpExecutor and Catalog metastore server

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • None
    • Impala 4.1.0
    • Catalog
    • None
    • ghx-label-8

    Description

      Currently, when doing create/drop table/db from catalogD, catalogOpExecutor (via Impala Shell) and metastore server (via HS2) acquires lock on their own respective lock objects to prevent concurrent create/drop operations in HMS. But that does not prevent these concurrent operations across CatalogOpExecutor and Metastore server. For example currently a user can perform create/drop HMS operation from Impala shell and catalog metastore server concurrently which is not the desired behavior

      Attachments

        Issue Links

          Activity

            People

              sourabh912 Sourabh Goyal
              sourabh912 Sourabh Goyal
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: