Help Center/ MapReduce Service/ FAQs/ Job Management/ What Can I Do If an Alarm is Generated Because the NameNode Is not Restarted on Time After the hdfs-site.xml File Is Modified?

Updated on 2024-08-16 GMT+08:00

View PDF

What Can I Do If an Alarm is Generated Because the NameNode Is not Restarted on Time After the hdfs-site.xml File Is Modified?

Question: What can I do if an alarm is generated because the NameNode is not restarted on time after the hdfs-site.xml file is modified?

Answer: If you do not restart the NameNode process after modifying the dfs.namenode.checkpoint.period parameter, an alarm may be falsely reported. In this case, you need to restart the NameNode process as soon as possible.

Parent topic: Job Management

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.

Chatbot