You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hbase.apache.org by "Bryan Beaudreault (Jira)" <ji...@apache.org> on 2022/08/26 11:02:00 UTC

[jira] [Commented] (HBASE-27332) Remove RejectedExecutionHandler for long/short compaction thread pools

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

Bryan Beaudreault commented on HBASE-27332:
-------------------------------------------

I feel like an OOME is a pretty bad failure mode for compaction queue buildup. Should we bound the queue? Maybe not a blocker for this issue, but might also change the approach if we decided to do that instead. 

> Remove RejectedExecutionHandler for long/short compaction thread pools
> ----------------------------------------------------------------------
>
>                 Key: HBASE-27332
>                 URL: https://issues.apache.org/jira/browse/HBASE-27332
>             Project: HBase
>          Issue Type: Improvement
>          Components: Compaction
>    Affects Versions: 3.0.0-alpha-3, 2.4.13
>            Reporter: Xiaolin Ha
>            Assignee: Xiaolin Ha
>            Priority: Minor
>             Fix For: 2.6.0, 3.0.0-alpha-4
>
>
> As disscussed in https://github.com/apache/hbase/pull/4725
> actually the max size of StealJobQueue is bouded by the VM limit of an array, and the OOM exception occurs before the rejection handler. So StealJobQueue is equivalent to be unbounded. I think the RejectionHandler may bring some confusions and make the codes a little puzzle.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)