Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Duplicate
-
2.1.0-beta
-
None
-
None
-
None
Description
The MapReduce AM is considering a forcibly preempted container as FAILED, while I think it should be considered as KILLED (i.e., not count against the maximum number of failures).
Attachments
Attachments
Issue Links
- relates to
-
MAPREDUCE-5900 Container preemption interpreted as task failures and eventually job failures
- Closed