[
https://issues.apache.org/jira/browse/HBASE-14272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14737194#comment-14737194
]
Lars Hofhansl commented on HBASE-14272:
---------------------------------------
Wait... Just wanted to make a patch and noticed that we already deal with TTL
correctly (as usually it pays to look at the code before making any statements,
a principle I violated this time).
Although, right now we compact every time when TTL is enable and there is a KV
old enough to be collected. So this is about how MIN_VERSIONS plays with that ,
and about time.to.purge.deletes.
I'm willing to let this slide now. What that means is that: (a) we might be
major compacting needlessly when MIN_VERSIONS is set, and (b) delete markers
might stay around forever when a major compaction within the
time.to.purge.deletes time range for a marker.
> Enforce major compaction on stores with TTL or time.to.purge.deletes enabled
> ----------------------------------------------------------------------------
>
> Key: HBASE-14272
> URL: https://issues.apache.org/jira/browse/HBASE-14272
> Project: HBase
> Issue Type: Bug
> Reporter: Vladimir Rodionov
> Assignee: Lars Hofhansl
> 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)
