[jira] [Commented] (MESOS-1988) Scheduler driver should not generate TASK_LOST when disconnected from master

["Marco Massenzio (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14582263#comment-14582263 ] 

Marco Massenzio commented on MESOS-1988:
----------------------------------------

[~vinod@twitter.com]:

I think that time has come :)
Can you please clarify what should the "expected" behavior be here?
Should the {{SchedulerDriver}} just wait to be reconnected or emit a {{TASK_DISCONNECTED}} event?

[~anandmazumdar] is ready to get going on this one, but we want to be sure what the fix ought to be.

Thanks!

> 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
>              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)