Hi Fred,
hm, if the bug dependents on Ubuntu version, my random guess is that it's
systemd related. Were you able to solve the problem? If not, it would be
helpful if you provide more context and describe a minimal setup that
reproduces the issue.
On Thu, Dec 10, 2015 at 10:15 AM, Frederic LE BRI
Thanks Alex.
About the context, we use spark on mesos and marathon to launch some
elastisearch,
I kill each leader one-by-one.
By the way as I said, we are on a config Mesos-Master on ubuntu 12, and
mesos-slave on ubuntu 14, to reproduce this comportement.
When I deploy only on Ubuntu 14 mast
Frederic,
I have skimmed through the logs and they are do not seem to be complete
(especially for master1). Could you please say what task has been killed
(id) and which master failover triggered that? I see at least three
failovers in the logs : ). Also, could you please share some background
abo
Hey Fred,
Logs (master and slave) can be helpful to sched some light on the problem.
On 2 Dec 2015 3:01 pm, "Frederic LE BRIS" wrote:
> Hi,
>
> I manage a Mesos Cluster 0.23.0 based on .deb from Mesosphere on Ubuntu
> 14.04.
>
> We deployed 3 zookeeper, 3 Mesos-master, and 3 Marathon : HA Mode
>
Hi,
I manage a Mesos Cluster 0.23.0 based on .deb from Mesosphere on Ubuntu 14.04.
We deployed 3 zookeeper, 3 Mesos-master, and 3 Marathon : HA Mode
And deployed 6 mesos slaves + slave process on 3 masters mesos.
So I have the following topology:
3 servers : Mesos-master / Marathon
3 servers :
5 matches
Mail list logo