Details
-
Epic
-
Status: Accepted
-
Major
-
Resolution: Unresolved
-
None
-
None
-
Default Executor improvements
Attachments
Attachments
Issues in epic
|
MESOS-8679 | If the first KILL stuck in the default executor, all other KILLs will be ignored. | Resolved | Unassigned | ||
|
MESOS-8537 | Default executor doesn't wait for status updates to be ack'd before shutting down | Resolved | Andrei Budnik | ||
MESOS-8927 | Default executor cannot kill tasks if `LAUNCH_NESTED_CONTAINER` is stuck. | Accepted | Unassigned | |||
MESOS-9052 | Default executor should commit suicide if it cannot receive HTTP responses for LAUNCH_NESTED_CONTAINER calls. | Open | Gastón Kleiman | |||
|
MESOS-8468 | `LAUNCH_GROUP` failure tears down the default executor. | Resolved | Gastón Kleiman | ||
|
MESOS-8530 | Default executor tasks can get stuck in KILLING state | Resolved | Gastón Kleiman | ||
MESOS-8531 | Some task status updates sent by the default executor don't contain a REASON. | Accepted | Unassigned | |||
MESOS-8532 | The default executor doesn't retry kills that it initiated | Accepted | Unassigned | |||
MESOS-8543 | The default executor can wrongly indicate that tasks from all task groups are unhealthy | Accepted | Unassigned | |||
MESOS-8557 | Default executor should allow decreasing the escalation grace period of a terminating task | Accepted | Unassigned | |||
MESOS-8726 | Default executor doesn't retry SIGTERM kills | Accepted | Unassigned | |||
MESOS-9330 | Default executor can skip status updates | Accepted | Unassigned |
MESOS-8529
Default Executor improvements
false
MESOS-8529
Default Executor improvements