Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Received-SPF: pass (nike.apache.org: domain of james.defelice@gmail.com
 designates 209.85.223.174 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAAkWvAxAun_LKVu9yCQ_=qYva9BXHfw2fjqXz1GRQh_Tg=WzuQ@mail.gmail.com>
References: 
 <CA+-zrRLJn2PXAamzrBMuBYwnJX3k4OvYOxOFoNg81K_uCO+QaA@mail.gmail.com>
 <CAAkWvAxAun_LKVu9yCQ_=qYva9BXHfw2fjqXz1GRQh_Tg=WzuQ@mail.gmail.com>
From: James DeFelice <james.defelice@gmail.com>
Date: Sun, 15 Mar 2015 21:59:50 -0400
Message-ID: 
 <CA+-zrRKpn-+N8VU+i2jpE18D5WrtsyGSxOKd9PzU_fxn5gzZ7w@mail.gmail.com>
Subject: Re: executor source not set
To: dev <dev@mesos.apache.org>
Content-Type: multipart/alternative; boundary=001a113ee63ec67b5c05115e35c7

--001a113ee63ec67b5c05115e35c7
Content-Type: text/plain; charset=UTF-8

Thanks, I found the same. For some reason I'm not seeing a Source set in
the updates that the scheduler is receiving. The updates are being
generated via the mesos-go bindings. The bindings shouldn't matter since
the slave is supposed to fill in the blank. Not sure what's going on, needs
more investigation. FWIW I'm observing this on 0.21.0.

On Sun, Mar 15, 2015 at 9:55 PM, Vinod Kone <vinodkone@apache.org> wrote:

> It is enforced by the slave to be future proof (a future where there will
> be no executor driver).
>
> https://github.com/apache/mesos/blob/master/src/slave/slave.cpp#L2491
>
> On Sun, Mar 15, 2015 at 11:45 AM, James DeFelice <james.defelice@gmail.com
> >
> wrote:
>
> > Is there a reason that the native executor driver bindings don't check
> > for/enforce a TaskStatus.Source of SOURCE_EXECUTOR?
> >
> > https://github.com/apache/mesos/blob/master/src/exec/exec.cpp#L490
> >
> > Or is that supposed to be handled somewhere else?
> >
> > -James
> >
>


-- 
James DeFelice
585.241.9488 (voice)
650.649.6071 (fax)

--001a113ee63ec67b5c05115e35c7--