Details
-
Sub-task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
2.1.0-beta
-
None
-
Reviewed
Description
With the current behavior is impossible to determine if a container has been preempted or lost due to a NM crash.
Adding a PREEMPTED exit status (-102) will help an AM determine that a container has been preempted.
Note the change of scope from the original summary/description. The original scope proposed API/behavior changes. Because we are passed 2.1.0-beta I'm reducing the scope of this JIRA.