mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Neil Conway (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-6785) CHECK failure on duplicate task IDs
Date Wed, 14 Dec 2016 00:40:59 GMT

     [ https://issues.apache.org/jira/browse/MESOS-6785?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Neil Conway updated MESOS-6785:
-------------------------------
    Summary: CHECK failure on duplicate task IDs  (was: Prevent duplicate task IDs for partition-aware
frameworks)

> CHECK failure on duplicate task IDs
> -----------------------------------
>
>                 Key: MESOS-6785
>                 URL: https://issues.apache.org/jira/browse/MESOS-6785
>             Project: Mesos
>          Issue Type: Bug
>          Components: master
>            Reporter: Neil Conway
>            Assignee: Neil Conway
>              Labels: mesosphere
>
> Duplicate task IDs might occur in two situations with partition-aware frameworks:
> # The agent is partitioned and task X on that agent is marked unreachable. The framework
that proceeds to attempt to launch a new task with id X; the task launch should fail.
> # Same as above except that the master fails over before the task launch occurs. Because
the master doesn't know that there is already a task id X on the partitioned agent, it cannot
reasonably fail the task launch. Hence, when the agent re-registers, we probably need to kill
the task with id X on the re-registering agent. This is unfortunate, but I'm not sure I see
a feasible alternative.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message