HBASE-1070 Up default index interval in TRUNK and branch
git-svn-id: https://svn.apache.org/repos/asf/hadoop/hbase/branches/0.18@728237 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
00949213b8
commit
e3e678fe30
|
@ -10,6 +10,7 @@ Release 0.18.2 - Unreleased
|
|||
from org.apache.hadoop.hbase.DroppedSnapshotException
|
||||
HBASE-981 hbase.io.index.interval doesn't seem to have an effect;
|
||||
interval is 128 rather than the configured 32
|
||||
HBASE-1070 Up default index interval in TRUNK and branch
|
||||
|
||||
IMPROVEMENTS
|
||||
HBASE-1046 Narrow getClosestRowBefore by passing column family (backport)
|
||||
|
|
|
@ -279,12 +279,13 @@
|
|||
</property>
|
||||
<property>
|
||||
<name>hbase.io.index.interval</name>
|
||||
<value>32</value>
|
||||
<value>128</value>
|
||||
<description>The interval at which we record offsets in hbase
|
||||
store files/mapfiles. Default for stock mapfiles is 128. Index
|
||||
files are read into memory. If there are many of them, could prove
|
||||
a burden. If so play with the hadoop io.map.index.skip property and
|
||||
skip every nth index member when reading back the index into memory.
|
||||
Downside to high index interval is lowered access times.
|
||||
</description>
|
||||
</property>
|
||||
<property>
|
||||
|
|
Loading…
Reference in New Issue