[
https://issues.apache.org/jira/browse/MESOS-5344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Neil Conway updated MESOS-5344:
-------------------------------
Description:
This epic covers three related tasks:
1. Allowing partitioned agents to reregister with the master. This allows
frameworks to control how tasks running on partitioned agents should be dealt
with.
2. Replacing the TASK_LOST task state with a set of more granular states with
more precise semantics: UNREACHABLE, DROPPED, UNKNOWN, GONE, and
GONE_BY_OPERATOR.
3. Allow frameworks to be informed when a task that was running on a
partitioned agent has been terminated (GONE and GONE_BY_OPERATOR states).
was:
This epic covers two related tasks:
1. Clarifying the semantics of TASK_LOST, and allow frameworks to learn when a
task is *truly* lost (i.e., not running), versus the current LOST semantics of
"may or may not be running".
2. Allowing frameworks to control how partitioned tasks are handled.
> Partition-aware Mesos frameworks
> --------------------------------
>
> Key: MESOS-5344
> URL: https://issues.apache.org/jira/browse/MESOS-5344
> Project: Mesos
> Issue Type: Epic
> Components: master
> Reporter: Neil Conway
> Assignee: Neil Conway
> Labels: mesosphere
>
> This epic covers three related tasks:
> 1. Allowing partitioned agents to reregister with the master. This allows
> frameworks to control how tasks running on partitioned agents should be dealt
> with.
> 2. Replacing the TASK_LOST task state with a set of more granular states with
> more precise semantics: UNREACHABLE, DROPPED, UNKNOWN, GONE, and
> GONE_BY_OPERATOR.
> 3. Allow frameworks to be informed when a task that was running on a
> partitioned agent has been terminated (GONE and GONE_BY_OPERATOR states).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
