Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
One orthogonal concern with issues like YARN-2055 and YARN-2022 is that AM containers getting preempted shouldn't count towards AM failures and thus shouldn't eventually fail applications.
We should explicitly handle AM container preemption/kill as a separate issue and not count it towards the limit on AM failures.
Attachments
Attachments
Issue Links
- is related to
-
MAPREDUCE-5956 MapReduce AM should not use maxAttempts to determine if this is the last retry
- Closed
-
YARN-2355 MAX_APP_ATTEMPTS_ENV may no longer be a useful env var for a container
- Resolved
- relates to
-
YARN-2055 Preemption: Jobs are failing due to AMs are getting launched and killed multiple times
- Resolved
-
YARN-611 Add an AM retry count reset window to YARN RM
- Closed
-
YARN-2022 Preempting an Application Master container can be kept as least priority when multiple applications are marked for preemption by ProportionalCapacityPreemptionPolicy
- Closed
-
YARN-614 Separate AM failures from hardware failure or YARN error and do not count them to AM retry count
- Closed