[jira] [Created] (IMPALA-12459) Try to avoid taking global version lock during HMS event processing

["Csaba Ringhofer (Jira)" <ji...@apache.org>]

Csaba Ringhofer created IMPALA-12459:
----------------------------------------

             Summary: Try to avoid taking global version lock during HMS event processing
                 Key: IMPALA-12459
                 URL: https://issues.apache.org/jira/browse/IMPALA-12459
             Project: IMPALA
          Issue Type: Improvement
          Components: Catalog
            Reporter: Csaba Ringhofer


Currently if the event is not filtered out by type and not disabled by table property then catalogd checks the database property which needs the version lock for a brief time:
https://github.com/apache/impala/blob/94f4f1d82461d8f71fbd0d2e9082aa29b5f53a89/fe/src/main/java/org/apache/impala/catalog/events/MetastoreEvents.java#L800
https://github.com/apache/impala/blob/94f4f1d82461d8f71fbd0d2e9082aa29b5f53a89/fe/src/main/java/org/apache/impala/catalog/CatalogServiceCatalog.java#L1303

Getting the readlock shouldn't be a problem in general, but it would be better if ignored events couldn't be blocked (for example rename can take the lock for a longer time). A solution could be to create a separate map and lock just for this property so that events could check it with a less contented lock.




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org