[
https://issues.apache.org/jira/browse/HBASE-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15759240#comment-15759240
]
Ajay Jadhav commented on HBASE-17280:
-------------------------------------
1. I'll change the name to be consistent with current convention-
setCleanerRunning.
2. Currently, the flag is present in CleanerChore. The purpose of this patch
was to make sure that we stop the periodic cleaner. By putting the flag in a
common place, the intention was to control the behavior of all the cleaners at
once. Can you please provide your reasoning for individual flags?
3. The enabled flag is only to make sure that the cleaner chore does not run
periodically. If someone calls the API explicitly, then we should allow cleaner
to run.
4. Yes, quite possible. Should I change it to debug or remove it?
> Add mechanism to control hbase cleaner behavior
> -----------------------------------------------
>
> Key: HBASE-17280
> URL: https://issues.apache.org/jira/browse/HBASE-17280
> Project: HBase
> Issue Type: Improvement
> Components: Client, hbase, shell
> Affects Versions: 2.0.0, 1.2.0
> Reporter: Ajay Jadhav
> Priority: Minor
> Fix For: 2.0.0, 1.2.0
>
> Attachments: HBASE-17280.branch-1.2.patch,
> HBASE-17280.branch-2.0.patch
>
>
> Cleaner is used to get rid of archived HFiles and old WALs in HBase.
> In the case of heavy workload, cleaner can affect query performance by
> creating a lot of connections to perform costly reads/ writes against
> underlying filesystem.
> This patch allows the user to control HBase cleaner behavior by providing
> shell commands to enable/ disable and manually run it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
