You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Gavin (JIRA)" <ji...@apache.org> on 2019/04/29 09:27:21 UTC
[jira] [Issue Comment Deleted] (MESOS-8768) Provide custom reason
for cascaded kill in a task group
[ https://issues.apache.org/jira/browse/MESOS-8768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin updated MESOS-8768:
-------------------------
Comment: was deleted
(was: www.rtat.net)
> Provide custom reason for cascaded kill in a task group
> -------------------------------------------------------
>
> Key: MESOS-8768
> URL: https://issues.apache.org/jira/browse/MESOS-8768
> Project: Mesos
> Issue Type: Improvement
> Components: scheduler api
> Reporter: Zhitao Li
> Priority: Major
> Labels: integration, observability
>
> Currently, if a task fails in a task group, other active tasks in the same group will see _TASK_KILLED_ without any custom reason. We would like to provide a custom reason like _*REASON_TASK_GROUP_KILLED*_ to distinguish whether the task is killed upon request of scheduler or upon a cascaded failure.
>
> Open question: does any framework depends the value of this reason? If not, we probably can just change the reason without a opt-in mechanism from framework (i.e, a new framework capability).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)