HBASE-11226 Document and increase the default value for hbase.hstore.flusher.count

This commit is contained in:
Nicolas Liochon 2014-05-23 19:28:51 +02:00
parent 8e13fea268
commit 28adf60658
2 changed files with 10 additions and 1 deletions

View File

@ -614,6 +614,15 @@ possible configurations would overwhelm and obscure the important.
is run to rewrite all HStoreFiles files as one. Larger numbers is run to rewrite all HStoreFiles files as one. Larger numbers
put off compaction but when it runs, it takes longer to complete.</description> put off compaction but when it runs, it takes longer to complete.</description>
</property> </property>
<property>
<name>hbase.hstore.flusher.count</name>
<value>2</value>
<description>
The number of flush threads. With less threads, the memstore flushes will be queued. With
more threads, the flush will be executed in parallel, increasing the hdfs load. This can
lead as well to more compactions.
</description>
</property>
<property> <property>
<name>hbase.hstore.blockingStoreFiles</name> <name>hbase.hstore.blockingStoreFiles</name>
<value>10</value> <value>10</value>

View File

@ -122,7 +122,7 @@ class MemStoreFlusher implements FlushRequester {
this.blockingWaitTime = conf.getInt("hbase.hstore.blockingWaitTime", this.blockingWaitTime = conf.getInt("hbase.hstore.blockingWaitTime",
90000); 90000);
int handlerCount = conf.getInt("hbase.hstore.flusher.count", 1); int handlerCount = conf.getInt("hbase.hstore.flusher.count", 2);
this.flushHandlers = new FlushHandler[handlerCount]; this.flushHandlers = new FlushHandler[handlerCount];
LOG.info("globalMemStoreLimit=" + LOG.info("globalMemStoreLimit=" +
StringUtils.humanReadableInt(this.globalMemStoreLimit) + StringUtils.humanReadableInt(this.globalMemStoreLimit) +