[
https://issues.apache.org/jira/browse/IMPALA-1628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Armstrong updated IMPALA-1628:
----------------------------------
Priority: Major (was: Critical)
> Improve synchronization protocol in the catalog
> -----------------------------------------------
>
> Key: IMPALA-1628
> URL: https://issues.apache.org/jira/browse/IMPALA-1628
> Project: IMPALA
> Issue Type: Improvement
> Components: Catalog
> Affects Versions: Impala 2.0.1, Impala 2.3.0
> Reporter: Dimitris Tsirogiannis
> Priority: Major
> Labels: catalog-server, impala
>
> Currently, the locking protocol used in the catalog is ad-hoc, hard to reason
> about, and doesn't provide well defined consistency guarantees. The
> lock-based protocol that is currently used is causing long writers (e.g.
> REFRESH) to block readers and the granularity of locks used is too coarse. We
> should reconsider the synchronization protocol used to protect the internal
> state of catalog objects. Different options could include:
> * Hierarchical locking
> * MVCC
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
