On 09/25/2015 04:34 PM, Raúl Gutiérrez Segalés wrote:
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
+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.
(then again, not a ZK expert here - if anyone knows better, please feel
free to
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.
>
Folks:
as a reminder, please be aware that as of Mesos 0.24.0, as announced back
in June, Mesos Master will write its information (`MasterInfo`) to
ZooKeeper in JSON format (see below for details).
If your framework relied on parsing the info (either de-serializing the
Protocol Buffer or just
On 09/25/2015 08:13 AM, Marco Massenzio wrote:
Folks:
as a reminder, please be aware that as of Mesos 0.24.0, as announced
back in June, Mesos Master will write its information (`MasterInfo`) to
ZooKeeper in JSON format (see below for details).
What versions of Zookeeper are supported by
James—
Marco will correct me if I'm wrong, but my understanding is that this
change does *not* impact what ZooKeeper version you can use with Mesos. We
have changed the format of the message stored in ZK from protobuf to JSON.
This message is needed by frameworks for mesos master leader
6 matches
Mail list logo