You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Reid Chan (JIRA)" <ji...@apache.org> on 2017/11/20 13:55:00 UTC
[jira] [Commented] (HBASE-19306) Avoid thread flood when both
LogCleaner and HFileCleaner support multi threads execution
[ https://issues.apache.org/jira/browse/HBASE-19306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259255#comment-16259255 ]
Reid Chan commented on HBASE-19306:
-----------------------------------
I have come up some ideas,
# since both cleaners share the same {{hbase.master.cleaner.interval}}, we can separate them by using different configs, like {{hbase.master.hfile.cleaner.interval}} and {{hbase.master.wal.cleaner.interval}}.
# or we can make use of the {{initialDelay}} which is not used by either of the cleaner chore.
Any thoughts?
> Avoid thread flood when both LogCleaner and HFileCleaner support multi threads execution
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-19306
> URL: https://issues.apache.org/jira/browse/HBASE-19306
> Project: HBase
> Issue Type: Improvement
> Components: wal
> Reporter: Reid Chan
>
> As discussion in HBASE-18309, it is possible that thread flood occurs when {{LogCleaner}} and {{HFileCleaner}} start their responsibility simultaneously in HMaster, worse case would drag NameNode down which would be the most unpleasant situation.
> We shall find a way to minimize the probability of that, or the better case, avoid that happening.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)