----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/51059/#review145776 -----------------------------------------------------------
Ship it! include/mesos/mesos.proto (lines 502 - 510) <https://reviews.apache.org/r/51059/#comment212135> This seems to suggest that we'll allow LAUNCH to also specify a command-less executor to get the default? That sounds good, but not sure if that was your intention. If it was, perhaps a TODO to have LAUNCH also allow a "default" command-less executor? (Ditto in v1) - Benjamin Mahler On Aug. 12, 2016, 11:08 p.m., Vinod Kone wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/51059/ > ----------------------------------------------------------- > > (Updated Aug. 12, 2016, 11:08 p.m.) > > > Review request for mesos, Benjamin Mahler, James DeFelice, and Jie Yu. > > > Bugs: MESOS-6036 > https://issues.apache.org/jira/browse/MESOS-6036 > > > Repository: mesos > > > Description > ------- > > This is done to allow schedulers to use `ExecutorInfo` with just > `executor_id` set. This is a requirement for the upcoming support > for `TaskGroup` semantics. > > Note that in this patch, TASK_ERROR is returned when > `ExecutorInfo.command` is unset to keep the existing semantics for > `LAUNCH` offer operation. This might change when we add `LAUNCH_GROUP` > operation. > > > Diffs > ----- > > include/mesos/mesos.proto af29dab2af4c28e257ad518c68d3f1af7cad0d06 > include/mesos/v1/mesos.proto a836f6e792944726ec6f8f66f77f403894377d05 > src/master/validation.cpp af18e5aef3be59830b0a7b0235bbc739dba1029c > src/tests/master_validation_tests.cpp > 9eb82a569f7c48caa96d4d54a93b199ccac74385 > > Diff: https://reviews.apache.org/r/51059/diff/ > > > Testing > ------- > > make check > > > Thanks, > > Vinod Kone > >