[
https://issues.apache.org/jira/browse/HBASE-25528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17275231#comment-17275231
]
Hudson commented on HBASE-25528:
--------------------------------
Results for branch branch-2
[build #166 on
builds.a.o|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/166/]:
(/) *{color:green}+1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/166/General_20Nightly_20Build_20Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/166/JDK8_20Nightly_20Build_20Report_20_28Hadoop2_29/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/166/JDK8_20Nightly_20Build_20Report_20_28Hadoop3_29/]
(/) {color:green}+1 jdk11 hadoop3 checks{color}
-- For more information [see jdk11
report|https://ci-hadoop.apache.org/job/HBase/job/HBase%20Nightly/job/branch-2/166/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}
> Dedicated merge dispatch threadpool on master
> ---------------------------------------------
>
> Key: HBASE-25528
> URL: https://issues.apache.org/jira/browse/HBASE-25528
> Project: HBase
> Issue Type: Improvement
> Components: master
> Affects Versions: 3.0.0-alpha-1, 1.7.0, 2.5.0
> Reporter: Bharath Vissapragada
> Assignee: Bharath Vissapragada
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.5.0, 2.3.5, 2.4.2
>
>
> Over the weekend we ran into an issue of running normalizer on a table with
> ~400k regions and we noticed the master was bottlenecked on merge dispatcher
> code that runs on a single threaded thread-pool that was meant for all master
> table operations (opcode: MASTER_TABLE_OPERATIONS). Having a dedicated
> thread-pool helped us dispatch merges at a faster rate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
