Folks, Based on some design feedback, I've modified the proposal for this feature.
Rather than introducing a new TASK_GONE status, the major change is to _change_ the meaning of TASK_LOST so that it only identifies when a task is definitely not running (either because it failed to launch or because the master knows it has shutdown). We'll introduce a new task state, TASK_LOST_IN_PROGRESS, for the case where a task may or may not be running (we've lost contact with the agent), but the master will instruct the slave to shutdown when it reconnects. More details here: https://docs.google.com/document/d/1D2mJnwuC1qlT_SJGspfj4MdAQXflESCqKANY0Pj4644 Neil On Mon, May 9, 2016 at 2:37 PM, Neil Conway <[email protected]> wrote: > Hi folks, > > To address some shortcomings and ambiguities in the TASK_LOST task > state, I'd like to propose that we introduce a new task state, > TASK_GONE. For more information, see the design doc: > > https://issues.apache.org/jira/browse/MESOS-5345 > > Comments welcome! > > Neil
