[
https://issues.apache.org/jira/browse/HBASE-14272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730275#comment-14730275
]
Lars Hofhansl commented on HBASE-14272:
---------------------------------------
hbase.hstore.time.to.purge.deletes is an extra mechanism to delay removal of
delete marker for a bit (mostly a hack to guard against bad timing of
compactions at a replication slave when edit can arrive out of order from the
master). It has nothing to do with KEEP_DELETED_CELLS.
KEEP_DELETED_CELLS makes the effect worse in this scenario. Not only the delete
markers would be hanging around, but also the data they mark for delete.
> Enforce major compaction on stores with KEEP_DELETED_CELLS=true
> ---------------------------------------------------------------
>
> Key: HBASE-14272
> URL: https://issues.apache.org/jira/browse/HBASE-14272
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Vladimir Rodionov
> Fix For: 2.0.0
>
> Attachments: HBASE-14272-v2.patch, HBASE-14272.patch
>
>
> Currently, if store has one (major compacted) file, the only case when major
> compaction will be triggered for this file again - when locality is below
> threshold, defined by *hbase.hstore.min.locality.to.skip.major.compact* or
> TTL expired some cells. If file has locality greater than this threshold it
> will never be major compacted until Store's TTL kicks in. For CF with
> KEEP_DELETED_CELLS on, compaction must be enabled always (even for single
> file), regardless of locality, when deleted cells are expired
> (*hbase.hstore.time.to.purge.deletes*)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
