You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2019/09/02 09:35:00 UTC

[jira] [Updated] (HBASE-22760) Stop/Resume Snapshot Auto-Cleanup activity with shell command

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

Guanghao Zhang updated HBASE-22760:
-----------------------------------
    Fix Version/s:     (was: 2.2.1)
                   2.2.2

> Stop/Resume Snapshot Auto-Cleanup activity with shell command
> -------------------------------------------------------------
>
>                 Key: HBASE-22760
>                 URL: https://issues.apache.org/jira/browse/HBASE-22760
>             Project: HBase
>          Issue Type: Improvement
>          Components: Admin, shell, snapshots
>    Affects Versions: 3.0.0, 1.5.0, 2.3.0
>            Reporter: Viraj Jasani
>            Assignee: Viraj Jasani
>            Priority: Major
>             Fix For: 3.0.0, 1.5.0, 2.3.0, 1.4.11, 2.1.7, 2.2.2
>
>         Attachments: HBASE-22760.branch-1.000.patch, HBASE-22760.branch-2.000.patch, HBASE-22760.master.003.patch, HBASE-22760.master.004.patch, HBASE-22760.master.005.patch, HBASE-22760.master.008.patch, HBASE-22760.master.009.patch
>
>
> For any scheduled snapshot backup activity, we would like to disable auto-cleaner for snapshot based on TTL. However, as per HBASE-22648 we have a config to disable snapshot auto-cleaner: hbase.master.cleaner.snapshot.disable, which would take effect only upon HMaster restart just similar to any other hbase-site configs.
> For any running cluster, we should be able to stop/resume auto-cleanup activity for snapshot based on shell command. Something similar to below command should be able to stop/start cleanup chore:
> hbase(main):001:0> snapshot_auto_cleanup_switch false    (disable auto-cleaner)
> hbase(main):001:0> snapshot_auto_cleanup_switch true     (enable auto-cleaner)



--
This message was sent by Atlassian Jira
(v8.3.2#803003)