[
https://issues.apache.org/jira/browse/HBASE-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795716#action_12795716
]
Jean-Daniel Cryans commented on HBASE-2087:
-------------------------------------------
Another thing to keep in mind, flushing incomplete memstores is highly
inefficient. Let's say you want to drop the number of WALs by flushing 10
regions. Those are probably not full, maybe 2MB or 10MB big, but they still
take time to flush and clogger HDFS with even more new files. Those files then
have to be compacted, it's even worse if we hit the "Too many store files"
problem and it's likely that one causes the other.
> The wait on compaction because "Too many store files" holds up all flushing
> ---------------------------------------------------------------------------
>
> Key: HBASE-2087
> URL: https://issues.apache.org/jira/browse/HBASE-2087
> Project: Hadoop HBase
> Issue Type: Bug
> Reporter: stack
>
> The method MemStoreFlusher#checkStoreFileCount is called from flushRegion.
> flushRegion is called by MemStoreFlusher#run thread. If the
> checkStoreFileCount finds too many store files, it'll stick around waiting on
> a compaction to happen. While its hanging, the MemStoreFlusher#run is held
> up. No other region can flush. Meantime WALs will be rolling and memory
> will be accumulating writes.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
