[
https://issues.apache.org/jira/browse/HBASE-15454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15236634#comment-15236634
]
Clara Xiong commented on HBASE-15454:
-------------------------------------
hbase.hstore.compaction.date.tiered.max.storefile.age.millis is the config you
need. In my implementation, windows will not be tiered/combined once they cross
this point of time, whether for minor or major compaction. Archive process can
use this too. Could you explain more why you need to concat the windows across
the max age point? My understanding is that once the maxTimestamp of file is
older than max age, it can be archived. It doesn't mean a file with a time span
across the point MUST be archived. This way the files will stay in the same
size of the highest tier.
I am out on a trip. I will read more closely tomorrow evening on the new
window implementation to see if I miss anything.
> Archive store files older than max age
> --------------------------------------
>
> Key: HBASE-15454
> URL: https://issues.apache.org/jira/browse/HBASE-15454
> Project: HBase
> Issue Type: Sub-task
> Components: Compaction
> Affects Versions: 2.0.0, 1.3.0, 0.98.18, 1.4.0
> Reporter: Duo Zhang
> Assignee: Duo Zhang
> Fix For: 2.0.0, 1.3.0, 0.98.19, 1.4.0
>
> Attachments: HBASE-15454-v1.patch, HBASE-15454.patch
>
>
> Sometimes the old data is rarely touched but we can not remove it. So archive
> it to several big files(by year or something) and use EC to reduce the
> redundancy.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
