Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-11734 Document changed behavior of hbase.hstore.time.to.purge.deletes (Misty Stanley-Jones)

This commit is contained in:
Jonathan M Hsieh 2014-08-18 13:31:32 -07:00
parent bf5eac49a9
commit 5b2069b7c9
2 changed files with 26 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
hbase-common/src/main/resources/hbase-default.xml
View File

@ -714,6 +714,15 @@ possible configurations would overwhelm and obscure the important.
or compacting. Do less if big KeyValues and problems with OOME. or compacting. Do less if big KeyValues and problems with OOME.
Do more if wide, small rows.</description> Do more if wide, small rows.</description>
</property> </property>
<property>
<name>hbase.hstore.time.to.purge.deletes</name>
<value>0</value>
<description>The amount of time to delay purging of delete markers with future timestamps. If
unset, or set to 0, all delete markers, including those with future timestamps, are purged
during the next major compaction. Otherwise, a delete marker is kept until the major compaction
which occurs after the marker's timestamp plus the value of this setting, in milliseconds.
</description>
</property>
<property> <property>
<name>hbase.storescanner.parallel.seek.enable</name> <name>hbase.storescanner.parallel.seek.enable</name>
<value>false</value> <value>false</value>

24
src/main/docbkx/book.xml
View File

@ -811,13 +811,23 @@ htable.put(put);
list.</para> list.</para>
<para>Also see <xref <para>Also see <xref
linkend="keyvalue" /> for more information on the internal KeyValue format. </para> linkend="keyvalue" /> for more information on the internal KeyValue format. </para>
<para>Delete markers are purged during the major compaction of store, unless the <para>Delete markers are purged during the next major compaction of the store, unless the
KEEP_DELETED_CELLS is set in the column family. In some scenarios, users want to keep <option>KEEP_DELETED_CELLS</option> option is set in the column family. To keep the
the deletes for a time and you can set the delete TTL: deletes for a configurable amount of time, you can set the delete TTL via the
hbase.hstore.time.to.purge.deletes in the configuration. If this delete TTL is not set, <option>hbase.hstore.time.to.purge.deletes</option> property in
or set to 0, all delete markers including those with future timestamp are purged during <filename>hbase-site.xml</filename>. If
the later major compaction. Otherwise, a delete marker is kept until the major <option>hbase.hstore.time.to.purge.deletes</option> is not set, or set to 0, all
compaction after marker's timestamp + delete TTL. </para> delete markers, including those with timestamps in the future, are purged during the
next major compaction. Otherwise, a delete marker with a timestamp in the future is kept
until the major compaction which occurs after the time represented by the marker's
timestamp plus the value of <option>hbase.hstore.time.to.purge.deletes</option>, in
milliseconds. </para>
<note>
<para>This behavior represents a fix for an unexpected change that was introduced in
HBase 0.94, and was fixed in <link
xlink:href="https://issues.apache.org/jira/browse/HBASE-10118">HBASE-10118</link>.
The change has been backported to HBase 0.94 and newer branches.</para>
</note>
</section> </section>
</section> </section>