hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (HBASE-16842) Chaos policies can terminate all masters for extended periods of time
Date Fri, 14 Oct 2016 21:54:20 GMT

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

Andrew Purtell edited comment on HBASE-16842 at 10/14/16 9:53 PM:
------------------------------------------------------------------

bq. I should note we sometimes saw it with the calm monkey, as well. This would suggest stability
problems with the HBase master,

Yes. Let me try that too.


was (Author: apurtell):
> I should note we sometimes saw it with the calm monkey, as well. This would suggest stability
problems with the HBase master,

Yes. Let me try that too.

> Chaos policies can terminate all masters for extended periods of time
> ---------------------------------------------------------------------
>
>                 Key: HBASE-16842
>                 URL: https://issues.apache.org/jira/browse/HBASE-16842
>             Project: HBase
>          Issue Type: Bug
>          Components: integration tests
>            Reporter: Andrew Purtell
>
> Running ITBLL with the slowDeterministic monkey I observe our primary and backup masters
in the test cluster can be both shut down by signals followed by no attempt to start replacements
for an extended period of time. Meanwhile other actions continue to run that churn the regionserver
fleet. Other monkeys may enter a similar state, but I haven't observed it. The outcome of
the convergence of these behaviors is the eventual time out and termination of the running
integration test, which is obvious and expected and unhelpful, so I believe unintentional.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message