Re: mesos agent not recovering after ZK init failure

On 9 February 2016 at 11:04, Sharma Podila wrote: > We had a few mesos agents stuck in an unrecoverable state after a > transient ZK init error. Is this a known problem? I wasn't able to find an > existing jira item for this. We are on 0.24.1 at this time. > > Most agents

Re: Fwd: [Breaking Change 0.24 & Upgrade path] ZooKeeper MasterInfo change.

On Sep 25, 2015 9:08 AM, "Marco Massenzio" wrote: > > +1 to what Alex says. > > As far as we know, the functionality we use (ephemeral sequential nodes and writing simple data to a znode) is part of the "base API" offered by ZooKeeper and every version would support it. >

Re: Mesos slaves across network zones

On 26 August 2014 08:49, Jeremy Jongsma jer...@barchart.com wrote: I think it makes sense for each datacenter to stay independently managed by a local Mesos master. But maybe a framework like Marathon could know about Marathon frameworks in other datacenters, and a Marathon app config could

Re: why does mesos require resolving all zookeeper hostnames?

On 30 July 2014 00:25, Itamar Ostricher ita...@yowza3d.com wrote: Thanks for the pointers! I'm not sure where in ZOOKEEPER-107 it says that, but I'll take your word for it :-) Any idea when 3.5 will be released? There's a release candidate due this week, so I am hoping some time in Aug.

Re: why does mesos require resolving all zookeeper hostnames?

On 29 July 2014 13:53, Benjamin Mahler benjamin.mah...@gmail.com wrote: Thanks for bringing this up! This is part of the ZK C library. We have seen failing slaves with sporadic DNS lookup failures in our clusters. After speaking to a ZK expert, I believe one of the things going into 3.5.0 is