[jira] [Commented] (HBASE-18083) Make large/small file clean thread number configurable in HFileCleaner

["Hudson (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720783#comment-16720783 ] 

Hudson commented on HBASE-18083:
--------------------------------

SUCCESS: Integrated in Jenkins build HBase-1.3-IT #509 (See [https://builds.apache.org/job/HBase-1.3-IT/509/])
HBASE-20559 Backport HBASE-18083 (Make large/small file clean thread (apurtell: rev 2434162594f22df0bba94bc40186bd5628501c8e)
* (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/master/cleaner/TestHFileCleaner.java
* (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/cleaner/HFileCleaner.java


> Make large/small file clean thread number configurable in HFileCleaner
> ----------------------------------------------------------------------
>
>                 Key: HBASE-18083
>                 URL: https://issues.apache.org/jira/browse/HBASE-18083
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Yu Li
>            Assignee: Yu Li
>            Priority: Major
>             Fix For: 2.0.0
>
>         Attachments: HBASE-18083.patch, HBASE-18083.v2.patch, HBASE-18083.v3.patch
>
>
> Currently we have only one thread for both large and small file cleaning, but when write pressure is huge we might need more cleaner threads, so we need to make the thread number configurable.
> We observed more than 1.8PB data in archive directory online due to business access rate change, and this proposal is one of the necessary changes required.
> Default value of the configurations would still be left to 1 to keep low pressure to NN for normal case.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)