Help Center> MapReduce Service> Component Operation Guide (ME-Abu Dhabi Region)> Using Yarn> Common Issues About Yarn> Why the Task Does Not Fail Even Though AppAttempts Restarts for More Than Two Times?

Updated on 2022-02-22 GMT+08:00

View PDF

Why the Task Does Not Fail Even Though AppAttempts Restarts for More Than Two Times?

Question

Why the task does not fail even though AppAttempts restarts due to failure for more than two times?

Answer

During the task execution process, if the ContainerExitStatus returns value ABORTED, PREEMPTED, DISKS_FAILED, or KILLED_BY_RESOURCEMANAGER, the system will not count it as a failed attempt. Therefore, the task fails only when the AppAttempts fails actually, that is, the return value is not ABORTED, PREEMPTED, DISKS_FAILED, or KILLED_BY_RESOURCEMANAGER for two times.

Parent topic: Common Issues About Yarn

Previous topic: Why Are Local Logs Not Deleted After YARN Is Restarted?

Next topic: Why Is an Application Moved Back to the Original Queue After ResourceManager Restarts?

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank 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.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.