[
https://issues.apache.org/jira/browse/HBASE-23615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17006276#comment-17006276
]
Hudson commented on HBASE-23615:
--------------------------------
Results for branch branch-2.2
[build #740 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/740/]:
(x) *{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/740//General_Nightly_Build_Report/]
(x) {color:red}-1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/740//JDK8_Nightly_Build_Report_(Hadoop2)/]
(/) {color:green}+1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/740//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Use a dedicated thread for executing WorkerMonitor in ProcedureExecutor.
> ------------------------------------------------------------------------
>
> Key: HBASE-23615
> URL: https://issues.apache.org/jira/browse/HBASE-23615
> Project: HBase
> Issue Type: Improvement
> Components: amv2
> Affects Versions: 2.2.2
> Reporter: Lijin Bin
> Assignee: Lijin Bin
> Priority: Major
> Fix For: 3.0.0, 2.3.0, 2.2.3
>
>
> See the discussion in https://issues.apache.org/jira/browse/HBASE-23597, it
> is better to have a dedicated thread for executing WorkerMonitor, so it will
> not blocked by other tasks.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
