[
https://issues.apache.org/jira/browse/MESOS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597096#comment-14597096
]
Bill Farner commented on MESOS-1988:
------------------------------------
Can someone describe what is to be gained by removing this behavior? I don't
agree that reconciliation is necessarily a replacement, as it is objectively
less responsive than the current near-immediate NACK from the TASK_LOST update.
Consistency guarantees aside (of course the framework needs to reconcile
either way); the proposed change seems like it is discarding a useful signal.
> 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: mesosphere, twitter
> Fix For: 0.24.0
>
>
> 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)
