[HBASE-21011] Provide CLI option to run oldwals and hfiles cleaner separately when cleaner chore is disabled

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 3.0.0-alpha-1, 1.4.6, 2.1.1
• Component/s: Admin, Client
• Assignee: Tak-Lon (Stephen) Wu
• Reporter: Tak-Lon (Stephen) Wu
• Created: 04/Aug/18 05:19
• Updated: 17/Aug/18 17:45
• Resolved: 17/Aug/18 17:45

Description

There is a corner case when cleaner chore for HFiles and oldwals is disabled, admin/user needs to manually execute admin command cleaner_chore_run to clean the old HFiles and oldwals. Existing logic of cleaner_chore_run is to firstly trigger the HFiles cleaner and then oldwals cleaner, and only return succeed if both completes. 

but when running this cleaner_chore_run command, there is a potential use case that admin would like trigger the cleaner for only oldwals or hfiles but still keep the automatic cleaner chore disabled. So, this change aims to provide support for this corner case, and provide flexibility for those user with cleaner chore disabled by default to execute admin CLI to run oldwals and HFiles cleaning procedure individually.

NOTE that cleaner_chore_run was introduced in HBASE-17280, this patch added options 'hfiles' and 'oldwals' to it. Also fix default behavior of cleaner_chore_run will be only ran when cleaner chore is set to disabled, e.g. the proposed admin CLI options are

hbase> cleaner_chore_run               # this was introduced in HBASE-17280, but changed the behavior to only ran when cleaner chore is set to disabled

hbase> cleaner_chore_run 'hfiles'      # added, ran when cleaner chore is set to disabled
hbase> cleaner_chore_run 'oldwals'     # added, ran when cleaner chore is set to disabled

Issue Links

• links to: Review Board (master)