[jira] [Comment Edited] (HBASE-17215) Separate small/large file delete threads in HFileCleaner to accelerate hfile cleanup speed

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

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

huaxiang sun edited comment on HBASE-17215 at 3/28/17 8:25 PM:
---------------------------------------------------------------

Hi [~carp84], we are seeing a case that cleaner is not fast enough to free up the disk space. Thought this jira can help in speeding up disk space clean. Do you mind post the patch? Thanks!


was (Author: huaxiang):
Hi [~carp84], we are seeing a case that cleaner is fast enough to free up the disk space. Thought this jira can help in speeding up disk space clean. Do you mind post the patch? Thanks!

> Separate small/large file delete threads in HFileCleaner to accelerate hfile cleanup speed
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-17215
>                 URL: https://issues.apache.org/jira/browse/HBASE-17215
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Yu Li
>            Assignee: Yu Li
>
> When using PCIe-SSD the flush speed will be really quick, and although we have per CF flush, we still have the {{hbase.regionserver.optionalcacheflushinterval}} setting and some other mechanism to avoid data kept in memory for too long to flush small hfiles. In our online environment we found the single thread cleaner kept cleaning earlier flushed small files while large files got no chance, which caused disk full then many other problems.
> Deleting hfiles in parallel with too many threads will also increase the workload of namenode, so here we propose to separate large/small hfile cleaner threads just like we do for compaction, and it turned out to work well in our cluster.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)