You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2014/11/20 01:13:34 UTC
[jira] [Updated] (MESOS-2127) killTask() should perform
reconciliation for unknown tasks.
[ https://issues.apache.org/jira/browse/MESOS-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Mahler updated MESOS-2127:
-----------------------------------
Component/s: master
Description:
Currently, {{killTask}} uses its own reconciliation logic, which has diverged from the {{reconcileTasks}} logic. Specifically, when the task is unknown and a non-strict registry is in use, {{killTask}} will not send TASK_LOST whereas {{reconcileTask}} will.
We should make these consistent.
was:
Currently, killTask() silently ignores the message if the task is not found and non-strict registry is in use. These semantics are different from reconcileTasks() which results in TASK_LOST in this case.
We need to make killTask() behavior consistent with reconcileTasks() and send TASK_LOST.
Issue Type: Improvement (was: Bug)
Summary: killTask() should perform reconciliation for unknown tasks. (was: killTask() should send TASK_LOST for unknown task and non-strict registry)
> killTask() should perform reconciliation for unknown tasks.
> -----------------------------------------------------------
>
> Key: MESOS-2127
> URL: https://issues.apache.org/jira/browse/MESOS-2127
> Project: Mesos
> Issue Type: Improvement
> Components: master
> Reporter: Vinod Kone
> Assignee: Benjamin Mahler
>
> Currently, {{killTask}} uses its own reconciliation logic, which has diverged from the {{reconcileTasks}} logic. Specifically, when the task is unknown and a non-strict registry is in use, {{killTask}} will not send TASK_LOST whereas {{reconcileTask}} will.
> We should make these consistent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)