You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Joe Smith (JIRA)" <ji...@apache.org> on 2012/10/25 04:18:12 UTC
[jira] [Updated] (MESOS-295) Allow new masters to have better
understanding of cluster state
[ https://issues.apache.org/jira/browse/MESOS-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Smith updated MESOS-295:
----------------------------
Description:
If a new master becomes elected, it will only have knowledge of the current state of the cluster. This can lead to a situation where tasks become lost but aren't properly killed. For instance:
1) A set of machines (perhaps a datacenter rack) lose network connectivity and their tasks are marked LOST by the master. However, they're still running.
2) Through a potentially unrelated situation, there is a master failover to a new master
3) The network connection to the machines come back up
4) These slaves never killed their tasks (and they shouldn't if they can't talk to a master)
5) Tasks stay running and aren't killed, taking up resources and running outside the scope of the new master
was:
1) machines lose network connectivity and their tasks are marked LOST
2) master failover to a new master
3) machines come back up
4) tasks stay running and aren't killed, taking up resources
Summary: Allow new masters to have better understanding of cluster state (was: Registrar to persist global state )
> Allow new masters to have better understanding of cluster state
> ---------------------------------------------------------------
>
> Key: MESOS-295
> URL: https://issues.apache.org/jira/browse/MESOS-295
> Project: Mesos
> Issue Type: Bug
> Reporter: Joe Smith
>
> If a new master becomes elected, it will only have knowledge of the current state of the cluster. This can lead to a situation where tasks become lost but aren't properly killed. For instance:
> 1) A set of machines (perhaps a datacenter rack) lose network connectivity and their tasks are marked LOST by the master. However, they're still running.
> 2) Through a potentially unrelated situation, there is a master failover to a new master
> 3) The network connection to the machines come back up
> 4) These slaves never killed their tasks (and they shouldn't if they can't talk to a master)
> 5) Tasks stay running and aren't killed, taking up resources and running outside the scope of the new master
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira