[
https://issues.apache.org/jira/browse/MESOS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14562894#comment-14562894
]
Benjamin Hindman edited comment on MESOS-2340 at 5/28/15 2:05 PM:
------------------------------------------------------------------
Just wanted to clarify the proposal here. [~xujyan] added labels in the past
exactly so we could go through deprecation cycles in a "safe" way. In other
words, the detector doesn't need to try and parse as JSON unless it's labeled
as JSON (e.g., 'info-json' or something). The deprecation cycle works exactly
the way [~vinodkone] and [~jvanremoortere] suggested but without the potential
false positives of trying to parse as JSON when it might not be JSON.
was (Author: benjaminhindman):
Just wanted to clarify the proposal here. We added labels in the past exactly
so we could go through deprecation cycles in a "safe" way. In other words,
there is no need to try and parse as JSON and then as protobuf: if it's not
labeled indicating it is JSON then we parse as protobuf. [~vinodkone],
[~xujyan], am I missing something here?
> 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: Marco Massenzio
>
> 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)
