You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2020/08/26 05:51:00 UTC
[jira] [Updated] (HBASE-24658) Update PolicyBasedChaosMonkey to
handle uncaught exceptions
[ https://issues.apache.org/jira/browse/HBASE-24658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guanghao Zhang updated HBASE-24658:
-----------------------------------
Fix Version/s: (was: 2.2.7)
2.2.6
> 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.6
>
>
> 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)