Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
When global memstore reaches the low water mark, we pick the best flushable region and flush all column families for it. This is a suboptimal approach in the sense that it leads to an unnecessarily high file creation rate and IO amplification due to compactions. We should still try to honor the underlying FlushPolicy.
Attachments
Attachments
Issue Links
- blocks
-
HBASE-17524 HBase 1.3.1 release
- Closed