[
https://issues.apache.org/jira/browse/MESOS-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Guilherme Moro updated MESOS-4010:
----------------------------------
Attachment: messages_node3.log
messages_node2.log
messages_node1.log
> Initial leader election unstable
> --------------------------------
>
> Key: MESOS-4010
> URL: https://issues.apache.org/jira/browse/MESOS-4010
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.25.0
> Environment: RHEL 6.6
> Reporter: Guilherme Moro
> Priority: Critical
> Attachments: messages_node1.log, messages_node2.log,
> messages_node3.log
>
>
> No leader is elected
> For a start, let me explain my setup:
> 3 nodes
> 3 zookeepers
> 3 mesos-master services, configured as initctl services and controlled by
> puppet, RPM's installed are from the RHEL repository at mesosphere (installed
> through puppet as well), running on RHEL 6.6
> Quorum is set to 2, as expected, all the remaining configs were double
> checked and appears to be correct.
> Most of times I can get the cluster to bootstrap after rebooting the nodes
> (sometimes more than once).
> The whole thing resembles a bit
> https://issues.apache.org/jira/browse/MESOS-2148 and
> https://issues.apache.org/jira/browse/MESOS-2014
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
