You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mengqing Peng (Jira)" <ji...@apache.org> on 2020/08/01 10:14:00 UTC

[jira] [Commented] (HBASE-15454) Freeze date tiered store files older than max age

    [ https://issues.apache.org/jira/browse/HBASE-15454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17169267#comment-17169267 ] 

Mengqing Peng commented on HBASE-15454:
---------------------------------------

We don't use this feature yet. Our cluster set `hbase.hstore.compaction.date.tiered.max.storefile.age.millis` to default (Long.Max). In most cases, opentsdb clusters need store 1 year data. 

> Freeze date tiered store files older than max age
> -------------------------------------------------
>
>                 Key: HBASE-15454
>                 URL: https://issues.apache.org/jira/browse/HBASE-15454
>             Project: HBase
>          Issue Type: New Feature
>          Components: Compaction
>    Affects Versions: 1.3.0, 0.98.18, 1.4.0, 2.0.0
>            Reporter: Duo Zhang
>            Assignee: Duo Zhang
>            Priority: Major
>             Fix For: 3.0.0-alpha-1
>
>         Attachments: HBASE-15454-v1.patch, HBASE-15454-v2.patch, HBASE-15454-v3.patch, HBASE-15454-v4.patch, HBASE-15454-v5.patch, HBASE-15454-v6.patch, HBASE-15454-v7.patch, HBASE-15454.patch
>
>
> In date tiered compaction, the store files older than max age are never touched by minor compactions. Here we introduce a 'freeze window' operation, which does the follow things:
> 1. Find all store files that contains cells whose timestamp are in the give window.
> 2. Compaction all these files and output one file for each window that these files covered.
> After the compaction, we will have only one in the give window, and all cells whose timestamp are in the give window are in the only file. And if you do not write new cells with an older timestamp in this window, the file will never be changed. This makes it easier to do erasure coding on the freezed file to reduce redundence. And also, it makes it possible to check consistency between master and peer cluster incrementally.
> And why use the word 'freeze'?
> Because there is already an 'HFileArchiver' class. I want to use a different word to prevent confusing.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)