You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "nicky paul sepnov (JIRA)" <ji...@apache.org> on 2015/08/02 07:24:04 UTC
[jira] [Commented] (MESOS-2340) Add ability to decode JSON
serialized MasterInfo from ZK
[ https://issues.apache.org/jira/browse/MESOS-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650611#comment-14650611 ]
nicky paul sepnov commented on MESOS-2340:
------------------------------------------
Hi can someone help me,
I have installed mesospshere with 3 as master and 2 as slave. But always error when choosing master.
Here i attach log from mesos-master, i have use mesos 0.24
Running on machine: master
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
W0802 11:50:42.346617 14567 authenticator.cpp:504] No credentials provided, authentication requests will be refused.
W0802 11:50:42.416157 14562 detector.cpp:444] Leading master master@192.168.70.2:5050 is using a Protobuf binary format when registering with ZooKeeper (info): this will be deprecated as of Mesos 0.24 (see MESOS-2340)
W0802 11:50:50.041250 14566 detector.cpp:444] Leading master master@192.168.70.3:5050 is using a Protobuf binary format when registering with ZooKeeper (info): this will be deprecated as of Mesos 0.24 (see MESOS-2340)
W0802 11:52:02.035001 14561 detector.cpp:444] Leading master master@192.168.70.4:5050 is using a Protobuf binary format when registering with ZooKeeper (info): this will be deprecated as of Mesos 0.24 (see MESOS-2340)
> Add ability to decode JSON serialized MasterInfo from ZK
> --------------------------------------------------------
>
> Key: MESOS-2340
> URL: https://issues.apache.org/jira/browse/MESOS-2340
> Project: Mesos
> Issue Type: Improvement
> Components: leader election
> Reporter: Zameer Manji
> Assignee: Marco Massenzio
> Labels: mesosphere
> Fix For: 0.23.0
>
>
> 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 ticket is an intermediate (compatibility) step: we add in {{0.23}} the ability for the {{Detector}} to "understand" JSON **alongside** Protobuf serialized format; this makes it compatible with both earlier versions, as well a future one (most likely, {{0.24}}) that will write the {{MasterInfo}} information in JSON format.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)