HBASE-1771 PE sequentialWrite is 7x slower because of MemStoreFlusher#checkStoreFileCount

git-svn-id: https://svn.apache.org/repos/asf/hadoop/hbase/trunk@805221 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jonathan Gray 2009-08-17 23:49:33 +00:00
parent caac328457
commit cff34ea9a4
2 changed files with 22 additions and 0 deletions

View File

@ -13,6 +13,8 @@ Release 0.21.0 - Unreleased
HBASE-1770 HTable.setWriteBufferSize does not flush the writeBuffer when HBASE-1770 HTable.setWriteBufferSize does not flush the writeBuffer when
its size is set to a value lower than its current size. its size is set to a value lower than its current size.
(Mathias via jgray) (Mathias via jgray)
HBASE-1771 PE sequentialWrite is 7x slower because of
MemStoreFlusher#checkStoreFileCount
OPTIMIZATIONS OPTIMIZATIONS

View File

@ -327,6 +327,26 @@
If too large, clients timeout during compaction. If too large, clients timeout during compaction.
</description> </description>
</property> </property>
<property>
<name>hbase.hstore.blockingStoreFiles</name>
<value>7</value>
<description>
If more than this number of StoreFiles in any one Store
(one StoreFile is written per flush of MemStore) then updates are
blocked for this HRegion until a compaction is completed, or
until hbase.hstore.blockingWaitTime has been exceeded.
</description>
</property>
<property>
<name>hbase.hstore.blockingWaitTime</name>
<value>90000</value>
<description>
The time an HRegion will block updates for after hitting the StoreFile
limit defined by hbase.hstore.blockingStoreFiles.
After this time has elapsed, the HRegion will stop blocking updates even
if a compaction has not been completed. Default: 90 seconds.
</description>
</property>
<property> <property>
<name>hbase.hstore.compaction.max</name> <name>hbase.hstore.compaction.max</name>
<value>10</value> <value>10</value>