----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/4433/#review6176 -----------------------------------------------------------
include/mesos/mesos.proto <https://reviews.apache.org/r/4433/#comment13294> How about something like: // Initial state, can not be transitioned to (via status updates). include/mesos/mesos.proto <https://reviews.apache.org/r/4433/#comment13295> Let's actually not change these numbers. Making TASK_STAGING be 6 is just fine. src/exec/exec.cpp <https://reviews.apache.org/r/4433/#comment13298> What about aborting the framework instead? src/master/master.cpp <https://reviews.apache.org/r/4433/#comment13296> You can kill these two checks if you'd prefer. src/slave/slave.cpp <https://reviews.apache.org/r/4433/#comment13297> Can kill these too (rather than making the complicated because of the weird number ordering). - Benjamin On 2012-03-21 17:43:24, Vinod Kone wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/4433/ > ----------------------------------------------------------- > > (Updated 2012-03-21 17:43:24) > > > Review request for mesos, Benjamin Hindman and John Sirois. > > > Summary > ------- > > To avoid ambiguity between the TASK_STARTING state that could be sent by the > executors, added a new TASK_STAGING state. > > This state should only be used by mesos core and a status update with this > state is explicitly disallowed from executors. > > > Diffs > ----- > > include/mesos/mesos.proto 478f561 > src/exec/exec.cpp 53f7e54 > src/master/http.cpp 628112b > src/master/master.cpp 6ae8aef > src/slave/http.cpp e259642 > src/slave/slave.hpp b7bc45a > src/slave/slave.cpp 9332caa > > Diff: https://reviews.apache.org/r/4433/diff > > > Testing > ------- > > make check > > > Thanks, > > Vinod > >
