Neil Conway created MESOS-6779:
----------------------------------
Summary: Consider rejecting reuse of task IDs
Key: MESOS-6779
URL: https://issues.apache.org/jira/browse/MESOS-6779
Project: Mesos
Issue Type: Improvement
Components: master
Reporter: Neil Conway
At present, frameworks are allowed to reuse task IDs, _if_ the previous task
with that ID has reached a terminal state. However, reusing task IDs is
discouraged, for two reasons:
# It is not always trivial to determine that a task has truly terminated, e.g.,
due to network partitions.
# Reusing task IDs makes it harder to interpret log files and diagnostic
information, since we generally assume that a task ID unambiguously identifies
a single task.
Rather than discouraging but supporting this behavior, we could instead have
the master try to reject attempts to reuse completed task IDs. Because the
master's list of completed tasks is a limited-size cache (which is not
preserved across master restart or failover), the master's checks for reusing
task IDs would likely be sound but not complete (i.e., we wouldn't be able to
catch _all_ situations in which completed task IDs are reused without paying a
prohibitive performance cost).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
