You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/06/28 01:46:25 UTC

[jira] [Closed] (MESOS-1200) Add SlaveID to KillTaskMessage to provide feedback for unknown slaves.

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

Benjamin Mahler closed MESOS-1200.
----------------------------------

    Resolution: Won't Fix

I'm going to close this as won't fix for now for a few reasons:

1. This seems like an edge case that reconciliation will provide a reliable solution for.
2. Leaving this out for now avoids an API change and keeps the API simple (frameworks only need to specify the TaskID for kill requests).
3. There are other cases where killTask requests are dropped. Reconciliation provides the general mechanism to check whether a killTask request took effect.

> Add SlaveID to KillTaskMessage to provide feedback for unknown slaves.
> ----------------------------------------------------------------------
>
>                 Key: MESOS-1200
>                 URL: https://issues.apache.org/jira/browse/MESOS-1200
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Benjamin Mahler
>
> In the presence of a strict Registry of slaves, we cannot inform the framework that the task was lost when the task is unknown (MESOS-783).
> To provide a TASK_LOST signal when a slave is unknown we need the KillTaskMessage to contain the SlaveID for the task. This will be considered optional but frameworks would be recommended to set this.



--
This message was sent by Atlassian JIRA
(v6.2#6252)