Change in Mesos leader info in ZK may break Mesos-DNS

[kozyraki]

Mesos 0.24 will follow this convention for the leading master info in ZK: https://github.com/mesos/commons/blob/master/docs/leader_discovery.rst
https://issues.apache.org/jira/browse/MESOS-2340
This will break existing Mesos-DNS code which assumes the old protobuf.

We need to update the code to handle correctly both 0.24 and older versions :(

[tsenart]

@kozyraki: As long as they maintain deprecated fields in the Protobufs for backwards compatibility (even if the data isn't filled), addressing this should be pretty easy. It'll be a great opportunity to properly encapsulate the master detection code behind a well defined API that hides these implementation and compatibility constraints.

[cmaloney]

This is currently preventing using Mesos 0.24 in DCOS. Needs to be fixed ASAP

[jdef]

I've started hacking on a patch in mesos-go

On Fri, Sep 11, 2015 at 1:00 AM, Cody Maloney [email protected]
wrote:

This is currently preventing using Mesos 0.24 in DCOS. Needs to be fixed
ASAP

—
Reply to this email directly or view it on GitHub
#228 (comment)
.

[jdef]

xref mesos/mesos-go#174

[tsenart]

@cmaloney: Would you please provide us with a more detailed timeline than ASAP?

[cmaloney]

It is going to delay multiple projects and likely make them miss their schedules if it is more than a couple business days out.

[tsenart]

@cmaloney: Thanks.

[jdef]

mesos-go/zk detection has been updated to support the JSON MasterInfo blob, need to incorporate updated Godeps into this project to pull the latest changes from mesos-go

[F21]

Ran into the problem while trying to use mesos-dns with mesos 0.24 today. Hope this gets merged soon!