[ https://issues.apache.org/jira/browse/HBASE-18083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16078002#comment-16078002 ]
Hudson commented on HBASE-18083: -------------------------------- FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #3331 (See [https://builds.apache.org/job/HBase-Trunk_matrix/3331/]) HBASE-18083 Make large/small file clean thread number configurable in (liyu: rev 4fe73857679ecba89a7edd3c17d9f92e4c0e2164) * (edit) hbase-server/src/main/java/org/apache/hadoop/hbase/master/cleaner/HFileCleaner.java * (edit) hbase-server/src/test/java/org/apache/hadoop/hbase/master/cleaner/TestHFileCleaner.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: Bug > Reporter: Yu Li > Assignee: Yu Li > Fix For: 2.0.0, 3.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 (v6.4.14#64029)