[ https://issues.apache.org/jira/browse/MESOS-5345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Neil Conway updated MESOS-5345: ------------------------------- Description: The TASK_LOST task status describes two different situations: (a) the task was not launched because of an error (e.g., insufficient available resources), or (b) the master lost contact with a running task (e.g., due to a network partition); the master will kill the task when it can (e.g., when the network partition heals), but in the meantime the task may still be running. This has two problems: 1. Using the same task status for two fairly different situations is confusing. 2. In the partitioned-but-still-running case, frameworks have no easy way to determine when a task has truly terminated. To address these problems, we propose introducing a new task status, TASK_LOST_IN_PROGRESS. If a framework opts into this behavior using a new capability, TASK_LOST would mean "the task is definitely not running", whereas TASK_LOST_IN_PROGRESS would mean "the task may or may not be running (we've lost contact with the agent), but the master will try to shut it down when possible." > Design doc for TASK_LOST_IN_PROGRESS > ------------------------------------ > > Key: MESOS-5345 > URL: https://issues.apache.org/jira/browse/MESOS-5345 > Project: Mesos > Issue Type: Task > Components: master > Reporter: Neil Conway > Labels: mesosphere > > The TASK_LOST task status describes two different situations: (a) the task > was not launched because of an error (e.g., insufficient available > resources), or (b) the master lost contact with a running task (e.g., due to > a network partition); the master will kill the task when it can (e.g., when > the network partition heals), but in the meantime the task may still be > running. > This has two problems: > 1. Using the same task status for two fairly different situations is > confusing. > 2. In the partitioned-but-still-running case, frameworks have no easy way to > determine when a task has truly terminated. > To address these problems, we propose introducing a new task status, > TASK_LOST_IN_PROGRESS. If a framework opts into this behavior using a new > capability, TASK_LOST would mean "the task is definitely not running", > whereas TASK_LOST_IN_PROGRESS would mean "the task may or may not be running > (we've lost contact with the agent), but the master will try to shut it down > when possible." -- This message was sent by Atlassian JIRA (v6.3.4#6332)