Help Center/ MapReduce Service/ Component Operation Guide (LTS)/ Using YARN/ Common Issues About Yarn/ Why Does Not a Task Fail After More Than Two Consecutive AppAttempts Failures?
Updated on 2025-11-13 GMT+08:00
Why Does Not a Task Fail After More Than Two Consecutive AppAttempts Failures?
Question
The default maximum number of AppAttempts failures is 2. Why does not a task fail after more than two consecutive AppAttempts failures during task execution?
Answer
During task execution, if the return value of ContainerExitStatus is ABORTED, PREEMPTED, DISKS_FAILED, or KILLED_BY_RESOURCEMANAGER, the system does not treat the attempt as a failed attempt.
As a result, the issue occurs. The task fails only after two genuinely failed attempts.
Parent topic: Common Issues About Yarn
What is your overall rating for this page?
0
1
2
3
4
5
6
7
8
9
10
Very dissatisfiedVery satisfied
Thank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
