[
https://issues.apache.org/jira/browse/HBASE-24658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17162404#comment-17162404
]
Hudson commented on HBASE-24658:
--------------------------------
Results for branch branch-2.2
[build #916 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/916/]:
(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/916//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/916//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/branch-2.2/916//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> Update PolicyBasedChaosMonkey to handle uncaught exceptions
> -----------------------------------------------------------
>
> Key: HBASE-24658
> URL: https://issues.apache.org/jira/browse/HBASE-24658
> Project: HBase
> Issue Type: Task
> Components: integration tests
> Reporter: Nick Dimiduk
> Assignee: Nick Dimiduk
> Priority: Minor
> Fix For: 3.0.0-alpha-1, 2.3.1, 1.7.0, 2.4.0, 2.2.7
>
>
> Running {{ServerKillingChaosMonkey}} via {{RESTApiClusterManager}} for any
> duration of time slowly leaks region servers. I see failures on the RESTApi
> side go unreported on the ChaosMonkey side. It seems like
> {{RuntimeExceptions}} are being thrown and lost.
> {{PolicyBasedChaosMonkey}} uses a primitive means of thread management
> anyway. Update to use a thread pool, thread groups, and an
> uncaughtExceptionHandler.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
