An update: I have a patch ready to land for MESOS-1143 <https://issues.apache.org/jira/browse/MESOS-1143>.
Before it lands, I'd like to solicit feedback as this changes the semantics for frameworks (for the better!). Any thoughts or reservations? On Tue, Nov 4, 2014 at 2:32 PM, Dominic Hamon <[email protected]> wrote: > As per MESOS-343 <https://issues.apache.org/jira/browse/MESOS-343>, the > TaskStatus now contains source and reason fields. These are set to allow > frameworks to differentiate between status updates that come from the > Master, Slave, or Executor, and to get more information in a programmatic > way about the update. This will be part of the 0.21.0 release. > > As a further enhancement, TASK_ERROR has been added (see MESOS-1143 > <https://issues.apache.org/jira/browse/MESOS-1143>) as part of 0.21.0. It > is not currently being sent, but will be in the next release (0.22.0) to > allow time for frameworks to support it. > > The semantics of TASK_LOST vs TASK_ERROR are simple: TASK_LOST means that > attempting to reschedule the task should succeed. TASK_ERROR means that any > attempt to reschedule the task will fail. This allows frameworks to make > better decisions. > > Thank you. > -- > Dominic Hamon | @mrdo | Twitter > *There are no bad ideas; only good ideas that go horribly wrong.* > -- Dominic Hamon | @mrdo | Twitter *There are no bad ideas; only good ideas that go horribly wrong.*
