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

Avoid write lock on the table during self-event detection

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: In Progress
    • Critical
    • Resolution: Unresolved
    • None
    • None
    • Catalog
    • None

    Description

      Saw some callstacks like this:

          at org.apache.impala.catalog.CatalogServiceCatalog.tryLock(CatalogServiceCatalog.java:468)
    at org.apache.impala.catalog.CatalogServiceCatalog.tryWriteLock(CatalogServiceCatalog.java:436)
    at org.apache.impala.catalog.CatalogServiceCatalog.evaluateSelfEvent(CatalogServiceCatalog.java:1008)
    at org.apache.impala.catalog.events.MetastoreEvents$MetastoreEvent.isSelfEvent(MetastoreEvents.java:609)
    at org.apache.impala.catalog.events.MetastoreEvents$BatchPartitionEvent.process(MetastoreEvents.java:1942)

      At this point it was already checked that the event comes from Impala based on service id and now we are checking the table's self event list. Taking the table lock can be problematic as other DDL may took write lock at the same time.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. IMPALA-12543 test_iceberg_self_events failed in JDK11 build

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              csringhofer Csaba Ringhofer
              csringhofer Csaba Ringhofer
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated: