我有三台机器m1、m2和m3。我在m1上部署了mesos master、zookeeper和marathon，在m2和m3上部署了mesos slave。但是，在mesos gui上，没有显示从机。然后我运行命令mesos resolve cat /etc/mesos/zk 检查slave是否发现了正确的master。但是不，它错误地发现127.0.0.1:5050是主。下面是上述命令的日志：

2015-07-31 15:38:02,522:17271(0x7f538b7cf700):ZOO_INFO@zookeeper_init@786: Initiating client connection, host=M1_IP:2181 sessionTimeout=10000 watcher=0x7f5392b130b0 sessionId=0 sessionPasswd=<null> context=0x7f5378003960 flags=0
2015-07-31 15:38:02,525:17271(0x7f5386dba700):ZOO_INFO@check_events@1703: initiated connection to server [M1_IP:2181]
2015-07-31 15:38:02,541:17271(0x7f5386dba700):ZOO_INFO@check_events@1750: session establishment complete on server [M1_IP:2181], sessionId=0x14ee590e0ec0008, negotiated timeout=10000
WARNING: Logging before InitGoogleLogging() is written to STDERR
I0731 15:38:02.541931 17273 group.cpp:313] Group process (group(1)@127.0.0.1:53978) connected to ZooKeeper
I0731 15:38:02.542022 17273 group.cpp:787] Syncing group operations: queue size (joins, cancels, datas) = (0, 0, 0)
I0731 15:38:02.542045 17273 group.cpp:385] Trying to create path '/mesos' in ZooKeeper
I0731 15:38:02.545756 17273 detector.cpp:138] Detected a new leader: (id='1')
I0731 15:38:02.545891 17273 group.cpp:656] Trying to get '/mesos/info_0000000001' in ZooKeeper
W0731 15:38:02.547034 17273 detector.cpp:444] Leading master master@127.0.0.1:5050 is using a Protobuf binary format when registering with ZooKeeper (info): this will be deprecated as of Mesos 0.24 (see MESOS-2340)
I0731 15:38:02.547114 17273 detector.cpp:481] A new leading master (UPID=master@127.0.0.1:5050) is detected

如日志所示，我在m1/zookeeper中查找了/mesos/info\u0000000001的节点值。结果是这样的：

!20150801-152910-16777343-5050-765???'"master@127.0.0.1:5050*
marathon-120.23.0

mesos主设置：cat/etc/mesos/zk

zk://M1_IP:2181/mesos

因此，看起来，mesos在m1掌握了一些如何不在zookeeper节点中存储其绝对ip的方法。有人能解释这种奇怪的行为吗。