The issue that was fixed recently was: https://issues.apache. org/jira/browse/MESOS-8135
This was a bug where we would lose track of executors (and their IDs) in the master for the non-command executor case. I believe it's still the case that command executors are not tracked in the master: https://issues.apache.org/jira/browse/MESOS-527 On Mon, Dec 18, 2017 at 3:30 PM, Vinod Kone <vinodk...@apache.org> wrote: > Where are you seeing `Task.executor_id` being empty? Can you show some logs > or API endpoint responses? > > There was a bug that Gaston fixed recently regarding executor ids being > incorrectly erased during re-registration. Not sure if it's related. > @Gaston, can you confirm? > > On Wed, Dec 13, 2017 at 1:39 PM, Eric Chung <ech...@uber.com> wrote: > > > Hello, > > > > I've noticed that when a task is launched with the command executor, the > > Task.executor_id field is empty, while the executor_id I get from the > > GET_EXECUTORS call matches Task.id. Is this expected behavior? Under what > > conditions would Task.executor_id be empty? > > > > Thanks! > > > > Eric > > >
