Details
-
New Feature
-
Status: Closed
-
Major
-
Resolution: Duplicate
-
None
-
None
-
None
-
None
Description
A store unit holds a column family in a region, where the memstore is its in-memory component. The memstore absorbs all updates to the store; from time to time these updates are flushed to a file on disk, where they are compacted. Unlike disk components, the memstore is not compacted until it is written to the filesystem and optionally to block-cache. This may result in underutilization of the memory due to duplicate entries per row, for example, when hot data is continuously updated.
Generally, the faster the data is accumulated in memory, more flushes are triggered, the data sinks to disk more frequently, slowing down retrieval of data, even if very recent.
In high-churn workloads, compacting the memstore can help maintain the data in memory, and thereby speed up data retrieval.
We suggest a new compacted memstore with the following principles:
1. The data is kept in memory for as long as possible
2. Memstore data is either compacted or in process of being compacted
3. Allow a panic mode, which may interrupt an in-progress compaction and force a flush of part of the memstore.
We suggest applying this optimization only to in-memory column families.
A design document is attached.
This feature was previously discussed in HBASE-5311.
Attachments
Attachments
Issue Links
- is related to
-
-
- Closed
-
-
HBASE-3149 Make flush decisions per column family
-
- Closed
-
-
-
- Closed
-
-
HBASE-14918 In-Memory MemStore Flush and Compaction
-
- Closed
-
- relates to
-
-
- Closed
-
- links to
