You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2018/08/16 22:21:00 UTC
[jira] [Assigned] (MESOS-9052) Default executor should commit
suicide if it cannot receive HTTP responses for LAUNCH_NESTED_CONTAINER
calls.
[ https://issues.apache.org/jira/browse/MESOS-9052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone reassigned MESOS-9052:
---------------------------------
Shepherd: Qian Zhang
Assignee: Gastón Kleiman
Story Points: 3
> Default executor should commit suicide if it cannot receive HTTP responses for LAUNCH_NESTED_CONTAINER calls.
> -------------------------------------------------------------------------------------------------------------
>
> Key: MESOS-9052
> URL: https://issues.apache.org/jira/browse/MESOS-9052
> Project: Mesos
> Issue Type: Bug
> Components: executor
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 1.7.0
> Reporter: Chun-Hung Hsiao
> Assignee: Gastón Kleiman
> Priority: Major
>
> If there is a network problem (e.g., a routing problem), it is possible that the agent has received {{LAUNCH_NESTED_CONTAINER}} calls from the default executor and launched the nested container, but the executor does not get the HTTP response. This would result in tasks stuck at {{TASK_STARTING}} forever. We should consider making the default executor commit suicide if it does not receive the response in a reasonable amount of time.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)