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

2015-09-25 Thread Marco Massenzio
Massenzio *Distributed Systems Engineerhttp://codetrips.com <http://codetrips.com>* -- Forwarded message -- From: Vinod Kone <vinodk...@gmail.com> Date: Wed, Jun 24, 2015 at 4:17 PM Subject: Re: [Breaking Change 0.24 & Upgrade path] ZooKeeper MasterInfo change. To: dev <

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

2015-06-24 Thread Vinod Kone
Just to clarify, any frameworks that are using the Mesos provided bindings (aka libmesos.so) should not worry, as long as the version of the bindings and version of the mesos master are not separated by more than 1 version. In other words, you should be able to live upgrade a cluster from 0.23.0

[Breaking Change 0.24 Upgrade path] ZooKeeper MasterInfo change.

2015-06-24 Thread Marco Massenzio
Folks, as heads-up, we are planning to convert the format of the MasterInfo information stored in ZooKeeper from the Protocol Buffer binary format to JSON - this is in conjunction with the HTTP API development, to allow frameworks *not* to depend on libmesos and other binary dependencies to