I'm having an issue restarting a downed slave.  I see this message in the
Master Logs about shutting down the slave.

Shutting down slave 20140929-033442-822441824-5050-13733-0 at
slave(1)@XXX.XXX.5.47:5051 (XXX.XXX.5.47) with message 'health check timed
out'

Now when I restart the slave it doesn't registered with the master, this is
all I see in the logs

I1210 14:35:58.518051 32273 status_update_manager.cpp:193] Recovering
status update manager
I1210 14:35:58.518538 32273 docker.cpp:577] Recovering Docker containers
I1210 14:35:58.519000 32271 containerizer.cpp:252] Recovering containerizer
I1210 14:35:58.521811 32271 group.cpp:313] Group process
(group(1)@XXX.XXX.5.47:5051) connected to ZooKeeper
I1210 14:35:58.521991 32271 group.cpp:787] Syncing group operations: queue
size (joins, cancels, datas) = (0, 0, 0)
I1210 14:35:58.522042 32271 group.cpp:385] Trying to create path '/mesos'
in ZooKeeper
I1210 14:35:58.526932 32271 detector.cpp:138] Detected a new leader:
(id='3')
I1210 14:35:58.527355 32271 group.cpp:658] Trying to get
'/mesos/info_0000000003' in ZooKeeper
I1210 14:35:58.529145 32273 detector.cpp:426] A new leading master
(UPID=mas...@xxx.xxx.5.49:5050) is detected
I1210 14:36:58.513636 32278 slave.cpp:3053] Current usage 60.91%. Max
allowed age: 2.036602219500185days


So it is detecting the correct master node, but I never see it try to
registered.  Do I need to do something different since the Master shut down
the slave previously???

-James

Reply via email to