[
https://issues.apache.org/jira/browse/MESOS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14549134#comment-14549134
]
Marco Massenzio commented on MESOS-2340:
----------------------------------------
The challenge here is that we write the ZNodes as {{ephemeral sequential}} - so
{{Master}} can only write one kind (currently, it uses, by default {{"info"}}
label): it can't write multiple labels/formats; nor it can write multiple
znodes and expect them to have the same sequence number (generally):
{noformat}
info_00001
json.info_00001 <-- it may (or may not) be from the same Master as info_00001
info_00002
json.info_00002 <-- ditto (00002)
info_00003
json.info_00003 <-- ditto (00003)
{noformat}
One possible approach would be to have one (and only one) separate process
(running, eg, on the Leader elected) that _watches_ the ZK _path_ given and
monitors creation/deletion of znodes; once it detects a new one (or changes to
an existing - is this even possible?), it will simply create one identically
named (but with, eg, a {{json}} prefix) and with the same info.
Similarly with node removals.
> 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)
