[
https://issues.apache.org/jira/browse/HBASE-17280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ajay Jadhav updated HBASE-17280:
--------------------------------
Affects Version/s: (was: 1.2.0)
1.0.0
Status: Patch Available (was: Reopened)
> 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: 1.0.0, 2.0.0
> Reporter: Ajay Jadhav
> Assignee: Ajay Jadhav
> Priority: Minor
> Fix For: 2.0.0
>
> Attachments: HBASE-17280.branch-1.001.patch,
> HBASE-17280.master.003.patch, HBASE-17280.master.004.patch,
> HBASE-17280.master.005.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.
> Our main intention with this patch was to avoid running the expensive cleaner
> chore during peak times. During our experimentation, we saw a lot of HFiles
> and WAL log related files getting created inside archive dir (didn't see
> ZKlock related files). Since we were replacing hdfs with S3, these delete
> calls will take forever to complete.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
