You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2015/05/26 22:44:41 UTC

[jira] [Issue Comment Deleted] (MESOS-2340) Publish JSON in ZK instead of serialized MasterInfo

     [ https://issues.apache.org/jira/browse/MESOS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vinod Kone updated MESOS-2340:
------------------------------
    Comment: was deleted

(was: +1

This echoes my comment at the very end of the doc.

```
Here's another (simpler) proposal? 

Can we just update the MasterDetector to try to parse the znode as json and if that returns an error try to parse it as proto? If we have that in 0.23.0, we can have the master just write json in 0.24.0.

```)

> Publish JSON in ZK instead of serialized MasterInfo
> ---------------------------------------------------
>
>                 Key: MESOS-2340
>                 URL: https://issues.apache.org/jira/browse/MESOS-2340
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Zameer Manji
>            Assignee: haosdent
>
> Currently to discover the master a client needs the ZK node location and access to the MasterInfo protobuf so it can deserialize the binary blob in the node.
> I think it would be nice to publish JSON (like Twitter's ServerSets) so clients are not tied to protobuf to do service discovery.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)