You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Nicolas Liochon (JIRA)" <ji...@apache.org> on 2014/05/21 19:06:41 UTC
[jira] [Updated] (HBASE-11208) Remove the
hbase.hstore.blockingStoreFiles setting
[ https://issues.apache.org/jira/browse/HBASE-11208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nicolas Liochon updated HBASE-11208:
------------------------------------
Summary: Remove the hbase.hstore.blockingStoreFiles setting (was: Remove the hbase.hstor.blockingStoreFiles setting)
> Remove the hbase.hstore.blockingStoreFiles setting
> --------------------------------------------------
>
> Key: HBASE-11208
> URL: https://issues.apache.org/jira/browse/HBASE-11208
> Project: HBase
> Issue Type: Brainstorming
> Components: Compaction, regionserver
> Affects Versions: 0.99.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 0.99.0
>
>
> It's a little bit of a provocation, but the rational is:
> - there are some bugs around the delayed flush. For example, if the periodic scheduler has asked for a delayed flush, and that we need to flush, we will have to wait
> - if the number of WAL files increases, we won't flush immediately if the blockingFile number has been reached. This impacts the MTTR.
> - We don't write to limit the compaction impact, but they are many cases where we would want to flush anyway, as the writes cannot wait.
> - this obviously leads to huge write latency peaks.
> So I'm questioning this setting, it leads to multiple intricate cases, unpredictable write latency, and looks like a workaround for compaction performances. With all the work done on compaction, I think we can get rid of it. A solution in the middle would be to deprecate it and to set it to a large value...
> Any opinion before I shoot :-) ?
--
This message was sent by Atlassian JIRA
(v6.2#6252)