You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2024/05/26 06:23:00 UTC

[jira] [Updated] (HBASE-28614) Introduce a field to display whether the snapshot is expired

     [ https://issues.apache.org/jira/browse/HBASE-28614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HBASE-28614:
-----------------------------------
    Labels: pull-request-available  (was: )

> Introduce a field to display whether the snapshot is expired
> ------------------------------------------------------------
>
>                 Key: HBASE-28614
>                 URL: https://issues.apache.org/jira/browse/HBASE-28614
>             Project: HBase
>          Issue Type: Improvement
>          Components: shell, snapshots, UI
>         Environment: hbase master
>            Reporter: guluo
>            Priority: Minor
>              Labels: pull-request-available
>
> HBase supports to create snapshot with TTL, and expired snapshots will be periodically deleted.
> This period is 30 min by default, as follow.
> {code:java}
> private static final String SNAPSHOT_CLEANER_INTERVAL = "hbase.master.cleaner.snapshot.interval";
> private static final int SNAPSHOT_CLEANER_DEFAULT_INTERVAL = 1800 * 1000; // Default 30 min {code}
>  
> Therefore, the following situation may occur: 
> The expired snapshot would still exist for a period of time on hbase cluster, and would not be deleted until the next operation of the periodic thread.
> So, Sometimes, we may use the expired snapshot because we donot know whether the snapshot is expired.
>  
> So, I think we can introduce a expired field for this situation in HBase UI.
> And on hbase shell ,adding snapshot TTL info and displaying expired if the snaphost has already expired.
> Or any better suggestions? Thanks a lot!



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