[jira] [Updated] (MESOS-4673) Agent fails to shutdown after re-registering period timed-out.

2016-03-29 Thread Artem Harutyunyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4673:
-
Sprint: Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere Sprint 31, 
Mesosphere Sprint 32  (was: Mesosphere Sprint 29, Mesosphere Sprint 30, 
Mesosphere Sprint 31)

> Agent fails to shutdown after re-registering period timed-out.
> --
>
> Key: MESOS-4673
> URL: https://issues.apache.org/jira/browse/MESOS-4673
> Project: Mesos
>  Issue Type: Bug
>  Components: docker
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere
>
> 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)

[jira] [Updated] (MESOS-4673) Agent fails to shutdown after re-registering period timed-out.

2016-03-15 Thread Artem Harutyunyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4673:
-
Sprint: Mesosphere Sprint 29, Mesosphere Sprint 30, Mesosphere Sprint 31  
(was: Mesosphere Sprint 29, Mesosphere Sprint 30)

> Agent fails to shutdown after re-registering period timed-out.
> --
>
> Key: MESOS-4673
> URL: https://issues.apache.org/jira/browse/MESOS-4673
> Project: Mesos
>  Issue Type: Bug
>  Components: docker
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere
>
> 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)

[jira] [Updated] (MESOS-4673) Agent fails to shutdown after re-registering period timed-out.

2016-03-01 Thread Artem Harutyunyan (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Harutyunyan updated MESOS-4673:
-
Sprint: Mesosphere Sprint 29, Mesosphere Sprint 30  (was: Mesosphere Sprint 
29)

> Agent fails to shutdown after re-registering period timed-out.
> --
>
> Key: MESOS-4673
> URL: https://issues.apache.org/jira/browse/MESOS-4673
> Project: Mesos
>  Issue Type: Bug
>  Components: docker
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere
>
> 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)

[jira] [Updated] (MESOS-4673) Agent fails to shutdown after re-registering period timed-out.

2016-02-25 Thread Benjamin Mahler (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Benjamin Mahler updated MESOS-4673:
---
Component/s: docker

> Agent fails to shutdown after re-registering period timed-out.
> --
>
> Key: MESOS-4673
> URL: https://issues.apache.org/jira/browse/MESOS-4673
> Project: Mesos
>  Issue Type: Bug
>  Components: docker
>Reporter: Jan Schlicht
>Assignee: Jan Schlicht
>  Labels: mesosphere
>
> 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)

[jira] [Updated] (MESOS-4673) Agent fails to shutdown after re-registering period timed-out.

2016-02-16 Thread Jan Schlicht (JIRA) 

 [ 
https://issues.apache.org/jira/browse/MESOS-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Schlicht updated MESOS-4673:

Summary: Agent fails to shutdown after re-registering period timed-out.  
(was: Agent fails to register after re-registering period timed-out.)

> Agent fails to shutdown 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
>  Labels: mesosphere
>
> 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)