[jira] [Commented] (HBASE-27565) Make the initial corePoolSize configurable for ChoreService

["Hudson (Jira)" <ji...@apache.org>]

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

Hudson commented on HBASE-27565:
--------------------------------

Results for branch branch-2.4
	[build #492 on builds.a.o|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/492/]: (x) *{color:red}-1 overall{color}*
----
details (if available):

(/) {color:green}+1 general checks{color}
-- For more information [see general report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/492/General_20Nightly_20Build_20Report/]


(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/492/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]


(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3) report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/492/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11 report|https://ci-hbase.apache.org/job/HBase%20Nightly/job/branch-2.4/492/JDK11_20Nightly_20Build_20Report_20_28Hadoop3_29/]


(/) {color:green}+1 source release artifact{color}
-- See build output for details.


(/) {color:green}+1 client integration test{color}


> Make the initial corePoolSize configurable for ChoreService
> -----------------------------------------------------------
>
>                 Key: HBASE-27565
>                 URL: https://issues.apache.org/jira/browse/HBASE-27565
>             Project: HBase
>          Issue Type: Improvement
>          Components: conf
>            Reporter: Peter Somogyi
>            Assignee: Peter Somogyi
>            Priority: Major
>             Fix For: 2.6.0, 3.0.0-alpha-4, 2.4.16, 2.5.3
>
>
> The initial corePoolSize for ChoreService is set to 1. The pool size is increased when a scheduled task misses its start time.
> On a cluster where the archive size is large, the HFileCleaner could run for a very long time and block the rest of the chores to run.
> By making the initial pool size configurable we could solve the bottleneck of caused by a long-running HFileCleaner chore.



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