[
https://issues.apache.org/jira/browse/HBASE-15454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238581#comment-15238581
]
Clara Xiong commented on HBASE-15454:
-------------------------------------
[~Apache9]I am trying to understand why the current DTCP doesn't work for you.
Is it because your archive window has to be calendar based?
I think we are on the same page that archiving/minor/major compaction process
should be independent of window implementation. The new config should move to
window config. Dave and I think you don't need to have a hybrid window which
use both exponential tiering and calendar based tiering. If someone really
wants calendar based window, we can support configs for each tier, including
number of window unit for each tier.
As to [~stack]'s question: This logic can be added to DTCP. Currently we do
have a config for store files that is no longer eligible for minor compaction,
which is max age. We can easily allow user to exclude these data from major
compaction/ region size calculation with a new config knob. Use can tweak DTCP
setting to keep file count very low or use any window implementation as they
like. DTCP has allowed plugged in compaction policy per window and default it
to exploring compaction policy. So the use can determine how many files they
want per window.
> 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)
