Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 29 Mar 2017 09:02:41 +0000 (UTC)
From: "Yu Li (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13024532.1480531160000.152200.1490778161763@Atlassian.JIRA>
In-Reply-To: <JIRA.13024532.1480531160000@Atlassian.JIRA>
References: <JIRA.13024532.1480531160000@Atlassian.JIRA> <JIRA.13024532.1480531160758@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HBASE-17215) Separate small/large file delete
 threads in HFileCleaner to accelerate hfile cleanup speed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 29 Mar 2017 09:02:46 -0000


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

Yu Li commented on HBASE-17215:
-------------------------------

Thanks for the reference [~anoop.hbase], will take a look when making the patch. The issue here exactly targets at accelerating cleaning the archived files, and changes will be mainly in HFileCleaner.

> 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)