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-08-22 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
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot
