[
https://issues.apache.org/jira/browse/IMPALA-14400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riza Suminto resolved IMPALA-14400.
-----------------------------------
Fix Version/s: Impala 5.0.0
Target Version: Impala 5.0.0
Resolution: Fixed
> Deadlock in CatalogServiceCatalog due to read lock upgrade to a write lock
> --------------------------------------------------------------------------
>
> Key: IMPALA-14400
> URL: https://issues.apache.org/jira/browse/IMPALA-14400
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 5.0.0
> Reporter: Riza Suminto
> Assignee: Riza Suminto
> Priority: Major
> Fix For: Impala 5.0.0
>
> Attachments: jstack_dump.txt
>
>
> test_metadata_after_failover_with_delayed_reset from a precommit jenkins job
> caught a case where CatalogD hang with deadlock during startup.
> This is easily hit when TRIGGER_RESET_METADATA_DELAY is increased to 3s. The
> reason is, EventProcessor attempt to obtain versionLock_.writeLock() in
> CatalogServiceCatalog.getDb() after obtaining versionLock_.readLock() in
> CatalogServiceCatalog.getDbProperty() (unsafe lock upgrade from read to
> write).
> [^jstack_dump.txt] shows the jstack when the deadlock occurs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
