Seeking a shepherd for MESOS-3408

Hi all, Is anyone willing to shepherd on MESOS-3408? Thanks! Regards, Qian Zhang

Re: Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

If we can land https://issues.apache.org/jira/browse/MESOS-3136 soon, it may be worth including in Mesos 0.24.1. There were also requests to backport the fix to Mesos 0.23.1. Any objections? On Mon, Sep 14, 2015 at 5:36 AM, tommy xiao wrote: > Cool Mesos team. > > 2015-09-14

Re: Seeking a shepherd for MESOS-3408

I'm on it. On Mon, Sep 14, 2015 at 11:14 PM, Qian AZ Zhang wrote: > > Hi all, > > Is anyone willing to shepherd on MESOS-3408? Thanks! > > > Regards, > Qian Zhang

Re: Proposing Mesos patch releases 0.21.2-0.24.1 for MESOS-2986

Woo/ 2015-09-15 14:39 GMT+08:00 Adam Bordelon : > If we can land https://issues.apache.org/jira/browse/MESOS-3136 soon, it > may be worth including in Mesos 0.24.1. > There were also requests to backport the fix to Mesos 0.23.1. Any > objections? > > On Mon, Sep 14, 2015 at

Re: Seeking a shepherd for MESOS-3408

Thanks Adam! Regards, Qian Zhang From: Adam Bordelon To: dev Date: 09/15/2015 14:43 Subject:Re: Seeking a shepherd for MESOS-3408 I'm on it. On Mon, Sep 14, 2015 at 11:14 PM, Qian AZ Zhang wrote: > > Hi

Why do we need slave_id in Kill message

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

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

The last comment (the one you cite) comes from a person, whose questions and answers you'd better verify : ). Having said that, let me try to answer your initial question. The master does not always know the SlaveID for each task. Imagine a master failover. In the registry there is just the a of

Re: Do we still need to add InverseOffer support to Scheduler API?

Thanks Anand for your clarification! I understand the intention now :-) BTW, what is future plan for the old C++ Scheduler/Scheduler Driver and also the Java/Python binding? Will we keep supporting them? Or they will be eventually deprecated in future? Regards, Qian Zhang From: Anand

Re: Do we still need to add InverseOffer support to Scheduler API?

Hi Qian, Yes, the eventual plan is to only support the (C++) Scheduler Library in the Mesos repository going forward and deprecate the old (C++/Java/Python) Scheduler/Scheduler Driver. The deprecation cycle “would/should" start after 1.0 is released. We would encourage the community to build

Re: Why do we need slave_id in Kill message

Thanks Alex. I checked the the comments in MESOS-1127, and based on the last comment (see below), it seems the question is still open ... > For me it looks like we can deduce SlaveID from TaskID modulo we have to wait for transitionary slaves. If this is the case, providing just TaskID in Kill and

Re: brew install mesos doesn't work for 0.24.0

hi @vinod Because we add python cli package in https://issues.apache.org/jira/browse/MESOS-3149 When you write the homebrew file, this line https://github.com/Homebrew/homebrew/blob/master/Library/Formula/mesos.rb#L98 >["native", "interface", ""].each do |p| should change to >["native",

Re: Why do we need slave_id in Kill message

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