[
https://issues.apache.org/jira/browse/MESOS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582715#comment-14582715
]
Vinod Kone commented on MESOS-1988:
-----------------------------------
My preference is for both the driver (src/sched/sched.cpp) and the library
(src/scheduler/scheduler.cpp) to silently drop the launchTask/acceptOffers
requests like they do every other request (e.g., killTask).
That said, this hack was originally added to the driver because prior to task
reconciliation schedulers didn't have a reliable way to know that these task
launches were dropped. Now, we need to make sure that the major frameworks out
there have implemented reconciliation and do not depend on this feature/hack.
cc [~maximk] [~connordoyle]. It's probably worth sending an email out to dev
list regarding this upcoming change (and maybe do the change in 24.0).
We can fix the library (scheduler.cpp) right away though, because we have not
officially released it. Maybe Anand can start on that one.
> Scheduler driver should not generate TASK_LOST when disconnected from master
> ----------------------------------------------------------------------------
>
> Key: MESOS-1988
> URL: https://issues.apache.org/jira/browse/MESOS-1988
> Project: Mesos
> Issue Type: Improvement
> Reporter: Vinod Kone
> Assignee: Anand Mazumdar
> Labels: twitter
>
> Currently, the driver replies to launchTasks() with TASK_LOST if it detects
> that it is disconnected from the master. After MESOS-1972 lands, this will be
> the only place where driver generates TASK_LOST. See MESOS-1972 for more
> context.
> This fix is targeted for 0.22.0 to give frameworks time to implement
> reconciliation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
