Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
Impala 2.0.1, Impala 2.3.0
-
None
Description
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
Attachments
Issue Links
- is blocked by
-
IMPALA-3127 Decouple partitions from tables
- Resolved
- relates to
-
IMPALA-2423 Concurrent operations on the same partitioned table may cause stale partition metadata
- Open