[
https://issues.apache.org/jira/browse/HBASE-14272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732052#comment-14732052
]
Andrew Purtell commented on HBASE-14272:
----------------------------------------
Yeah we should be collecting more information during compaction and consulting
it when deciding on the file later.
For TTL expiry work, during compaction we could identify the surviving cell
with the shortest lifetime and record in the file metadata the timestamp when
the expiration will take effect. When we're past that point in time later we
would know there is something to garbage collect.
> 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)
