[
https://issues.apache.org/jira/browse/HBASE-28614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Duo Zhang resolved HBASE-28614.
-------------------------------
Fix Version/s: 2.7.0
3.0.0-beta-2
2.6.1
2.5.9
Hadoop Flags: Reviewed
Resolution: Fixed
Pushed to all active branches.
Thanks [~guluo] for contributing!
> 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
> Assignee: guluo
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.7.0, 3.0.0-beta-2, 2.6.1, 2.5.9
>
>
> 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)
