You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Jean-Daniel Cryans (JIRA)" <ji...@apache.org> on 2010/01/01 02:02:29 UTC
[jira] Commented: (HBASE-2087) The wait on compaction because "Too
many store files" holds up all flushing
[ https://issues.apache.org/jira/browse/HBASE-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795715#action_12795715 ]
Jean-Daniel Cryans commented on HBASE-2087:
-------------------------------------------
So either we have too much WALs or too much store files right? Like I said in HBASE-2053, our WAL is set very small so that master splits fast and we don't lose data. In 0.21 we won't lose data so speeding up the spit time then set a higher/bigger WAL would solve this problem?
> 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.