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 to 0.24.0.
For framework schedulers that don't use the bindings (pesos, jesos etc), it is prudent to add support for JSON formatted ZNODE to their master detection code. Thanks, On Wed, Jun 24, 2015 at 4:10 PM, Marco Massenzio <ma...@mesosphere.io> wrote: > 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 > interact with Mesos Master nodes. > > *NOTE* - there is no change in 0.23 (so any Master/Slave/Framework that is > currently working in 0.22 *will continue to work* in 0.23 too) but as of > Mesos 0.24, frameworks and other clients relying on the binary format will > break. > > The details of the design are in this Google Doc: > > https://docs.google.com/document/d/1i2pWJaIjnFYhuR-000NG-AC1rFKKrRh3Wn47Y2G6lRE/edit > > the actual work is detailed in MESOS-2340: > https://issues.apache.org/jira/browse/MESOS-2340 > > and the patch (and associated test) are here: > https://reviews.apache.org/r/35571/ > https://reviews.apache.org/r/35815/ > > *Marco Massenzio* > *Distributed Systems Engineer* >
