You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "mahua (Jira)" <ji...@apache.org> on 2022/12/15 11:23:00 UTC

[jira] (HBASE-27537) Optimize the compaction triggering logic if table has set TTL

    [ https://issues.apache.org/jira/browse/HBASE-27537 ]


    mahua deleted comment on HBASE-27537:
    -------------------------------

was (Author: sujun):
Could you assign it to me

> Optimize the compaction triggering logic if  table has set TTL
> --------------------------------------------------------------
>
>                 Key: HBASE-27537
>                 URL: https://issues.apache.org/jira/browse/HBASE-27537
>             Project: HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 2.4.15
>            Reporter: mahua
>            Priority: Critical
>
> Although table has a TTL set in the cluster，some regions do not perform periodic major compactions，and the expired TTL data is still stored in these large files. Not trigger the reason is that the periodic check of the thread according to number of files in the region  If > hbase.hstore.compaction.min then major compaction is not triggered, Instead, minor compaction is triggered first. But minor compaction which excludes large files (by the hbase.hstore.compaction.max.size), when the larger files reach a certain number, the expired data under the larger files cannot be deleted normally.
>  
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)