You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Jan Schlicht (JIRA)" <ji...@apache.org> on 2016/02/15 10:26:18 UTC
[jira] [Created] (MESOS-4673) Agent fails to register after
re-registering period timed-out.
Jan Schlicht created MESOS-4673:
-----------------------------------
Summary: Agent fails to register after re-registering period timed-out.
Key: MESOS-4673
URL: https://issues.apache.org/jira/browse/MESOS-4673
Project: Mesos
Issue Type: Bug
Reporter: Jan Schlicht
Assignee: Jan Schlicht
Under certain conditions, when a mesos agent looses connection to the master for an extended period of time (Say a switch fails), the master will de-register the agent, and then when the agent comes back up, refuse to let it register: {{Slave asked to shut down by master@10.102.25.1:5050 because 'Slave attempted to re-register after removal'}}.
The agent doesn't seem to be able to properly shutdown and remove running tasks as it should do to register as a new agent. Hence this message will persist until it's resolved by manual intervetion.
This seems to be caused by Docker tasks that couldn't shutdown cleanly when the agent is asked to shutdown running tasks to be able to register as a new agent with the master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)