I asked the same question some time ago and got a good explanation from Ben
Mahler. Take a look at last comments in MESOS-1127
<https://issues.apache.org/jira/browse/MESOS-1127> and maybe even comments
in review requests.
Since the same question comes (at least) for the second time, maybe it
makes sense to persist the answer somewhere (a comment in the protobuf).
On Tue, Sep 15, 2015 at 11:55 AM, Klaus Ma <kl...@cguru.net> wrote:
> I think this slave_id is used for status sync up/double check. In master,
> it'll check whether the special slave_id is equal to task's slave id; if
> not equal, master log message and ignore kill request.
>
>
> On 2015年09月15日 17:46, Qian AZ Zhang wrote:
>
>> Hi,
>>
>> In Kill message (scheduler.proto), I found there is a slave_id field:
>> message Kill {
>> required TaskID task_id = 1;
>> optional SlaveID slave_id = 2;
>> }
>>
>> I am just wondering in which case framework needs to specify this field
>> when it kills a task, I think master should know the slave id of each
>> task,
>> can we just use the info in master?
>>
>>
>> Regards,
>> Qian Zhang
>>
>
> --
> Klaus Ma (马达), PMP® | http://www.cguru.net
>
>
