+vinod Hm.. I can't tell from MESOS-1988, why is this required for the HTTP API? I see MESOS-1972 as a link to more context, but that is for validation. The disconnected case does not overlap with the master's validation logic, it is an artifact of the driver implementation (the scheduler can't tell when it's launch calls are enqueued behind a disconnected event).
On Mon, Jun 22, 2015 at 5:23 PM, Anand Mazumdar <[email protected]> wrote: > Hi All, > > We intend to introduce a breaking change [1] in the driver to silently > ignore launchTasks/acceptOffers(…) calls when disconnected from the master > in 0.24. The previous behavior was to send out “TASK_LOST” messages since > there was no way to know that these task launches were dropped. However , > with the advent of Task Reconciliation, this feature is redundant. Other > calls like killTask/requestResource et al already had this behavior. > > If your existing framework relied on this behavior, I would encourage you > to use the Task Reconciliation API [2] in lieu of this feature/hack. Let me > know if you have any queries/concerns. > > Links: > [1] Tracking JIRA: https://issues.apache.org/jira/browse/MESOS-1988 < > https://issues.apache.org/jira/browse/MESOS-1988> > [2] Task Reconciliation API : > http://mesos.apache.org/documentation/latest/reconciliation/ < > http://mesos.apache.org/documentation/latest/reconciliation/> > > -anand
