[
https://issues.apache.org/jira/browse/MESOS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14550654#comment-14550654
]
Marco Massenzio commented on MESOS-2340:
----------------------------------------
I'm not familiar with the {{multi}} operation, however, thinking a bit more
about this, it turns out the solution should be simpler: post ephemeral node
creation, create another "mirror" JSON-content znode, equally ephemeral, that
will go away whenever the original PB-content znode does.
This seems a simple enough approach (and, as such, I'm sure I'm overlooking
something!)
I'm looking into the code, and it seems to me that the
{{GroupProcess::doJoin()}} is the place to do this (maybe?)
> 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)
