You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2015/02/17 01:53:13 UTC
[jira] [Commented] (MESOS-1988) Scheduler driver should not
generate TASK_LOST when disconnected from master
[ https://issues.apache.org/jira/browse/MESOS-1988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14323509#comment-14323509 ]
Niklas Quarfot Nielsen commented on MESOS-1988:
-----------------------------------------------
Hey [~vinodkone] - do you think this is an easy fix, or should we postpone?
> 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
>
> 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)