Help Center> MapReduce Service> Component Operation Guide (Normal)> Using YARN> Common Issues About Yarn> Why the Job Fails with HDFS_DELEGATION_TOKEN Expired Exception?

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

View PDF

Why the Job Fails with HDFS_DELEGATION_TOKEN Expired Exception?

Question

Why is the HDFS_DELEGATION_TOKEN expired exception reported when a job fails in security mode?

Answer

HDFS_DELEGATION_TOKEN expires because the token is not updated or it is accessed after max. lifetime.

Ensure the following parameter value of max. lifetime of the token is greater than the job running time.

dfs.namenode.delegation.token.max-lifetime=604800000 (1 week by default)

Go to the All Configurations page of HDFS by referring to Modifying Cluster Service Configuration Parameters and search for this parameter in the search box.

You are advised to set this parameter to a value that is multiple times of the number of hours within the max. lifecycle of the token.

Parent topic: Common Issues About Yarn

Previous topic: Why Mounted Directory for Container is Not Cleared After the Completion of the Job While Using CGroups?

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

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.