Re: Why do we need slave_id in Kill message

2015-09-23 Thread Benjamin Mahler
e: > > From: Alex Rukletsov <a...@mesosphere.com> > To: dev <dev@mesos.apache.org> > Date: 09/19/2015 21:12 > Subject: Re: Why do we need slave_id in Kill message > -- > > > > Inlined. > > On Sat, Sep 19, 2015 at 2:23 PM, Q

Re: Why do we need slave_id in Kill message

2015-09-20 Thread Qian AZ Zhang
Thanks Alex, it is clear to me now :-) Regards, Qian Zhang From: Alex Rukletsov <a...@mesosphere.com> To: dev <dev@mesos.apache.org> Date: 09/19/2015 21:12 Subject: Re: Why do we need slave_id in Kill message Inlined. On Sat, Sep 19, 2015 at 2:23 PM, Qian AZ

Re: Why do we need slave_id in Kill message

2015-09-19 Thread Alex Rukletsov
letsov ---09/16/2015 > 00:25:03---The last comment (the one you cite) comes from a person, whos]Alex > Rukletsov ---09/16/2015 00:25:03---The last comment (the one you cite) > comes from a person, whose questions and answers you'd better ve > > From: Alex Rukletsov <a..

Why do we need slave_id in Kill message

2015-09-15 Thread Qian AZ Zhang
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

Re: Why do we need slave_id in Kill message

2015-09-15 Thread Klaus Ma
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

Re: Why do we need slave_id in Kill message

2015-09-15 Thread Alex Rukletsov
sked the same question some time ago and got a good explan]Alex > Rukletsov ---09/15/2015 20:52:26---I asked the same question some time ago > and got a good explanation from Ben Mahler. Take a look at l > > From: Alex Rukletsov <a...@mesosphere.com> > To: dev <dev@mesos.apache

Re: Why do we need slave_id in Kill message

2015-09-15 Thread Qian AZ Zhang
eries than just state of tasks. message Task { required TaskID task_id = 1; optional AgentID agent_id = 2; } repeated Task tasks = 1; } Regards, Qian Zhang From: Alex Rukletsov <a...@mesosphere.com> To: dev <dev@mesos.apache.org> Date: 09/15/2015 20

Re: Why do we need slave_id in Kill message

2015-09-15 Thread Alex Rukletsov
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 and maybe even comments in review requests. Since the same question comes (at least) for the second time, maybe it