Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Cloudera Community

Community Articles

Find and share helpful community-sourced technical articles.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Advanced Search
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

Ambari Alert

Labels (2)
avatar
author-rank knarendran
Guru

Created on ‎07-14-2017 10:51 PM

Issue:

Sometimes ambari might throw the above alert which puts you in some confusion how all 50 DN's can be active and stale.

Firstly, I suggest you to go through this article from HCC and understand how to identify stale datanodes

Resolution:

Increase the value of the property from 30000(default) to 60000 milli seconds or 180000 milli seconds 

dfs.namenode.stale.datanode.interval=60000 or 180000
1,244 Views
0 Kudos
Announcements
Community Announcements
Community Upgrade Announcement
What's New @ Cloudera
Announcing Cloudera Flow Management Operator for Kubernetes ...
What's New @ Cloudera
Announcing Cloudera Streams Messaging Operator for Kubernete...
Community Announcements
July 2026 Community Highlights
Community Announcements
June 2026 Community Highlights
View More Announcements
Version history
Last update:
‎07-14-2017 10:51 PM
Updated by:
Guru
Contributors