[
https://issues.apache.org/jira/browse/MESOS-3280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701679#comment-14701679
]
haosdent edited comment on MESOS-3280 at 8/18/15 5:45 PM:
----------------------------------------------------------
The details about how aphyr test this is this article [Call me Maybe: Chrono |
https://aphyr.com/posts/326-call-me-maybe-chronos] It is on HN news first page
now. And other user asked in stackoverflow seems also because of this bug.
[mesos-master crash with zookeeper cluster |
http://stackoverflow.com/questions/32044884/mesos-master-crash-with-zookeeper-cluster]
was (Author: haosd...@gmail.com):
The details about how aphyr test this is this article [Call me Maybe:
Chronos](https://aphyr.com/posts/326-call-me-maybe-chronos) It is on HN news
first page now. And other user asked in stackoverflow seems also because of
this bug. [mesos-master crash with zookeeper
cluster](http://stackoverflow.com/questions/32044884/mesos-master-crash-with-zookeeper-cluster)
> Master fails to access replicated log after network partition
> -------------------------------------------------------------
>
> Key: MESOS-3280
> URL: https://issues.apache.org/jira/browse/MESOS-3280
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.23.0
> Environment: Zookeeper version 3.4.5--1
> Reporter: Bernd Mathiske
> Labels: mesosphere
>
> In a 5 node cluster with 3 masters and 2 slaves, and ZK on each node, when a
> network partition is forced, all the masters apparently lose access to their
> replicated log. The leading master halts. Unknown reasons, but presumably
> related to replicated log access. The others fail to recover from the
> replicated log. Unknown reasons. This could have to do with ZK setup, but it
> might also be a Mesos bug.
> This was observed in a Chronos test drive scenario described in detail here:
> https://github.com/mesos/chronos/issues/511
> With setup instructions here:
> https://github.com/mesos/chronos/issues/508
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
