Created 07-17-2017 10:05 AM
Hi,
@Bjorn Olsen, I saw your post on https://community.hortonworks.com/comments/102851/view.html where you have mentioned to increase the default alert_grace_period=5 to 10 to get rid of stale alert in Ambari-2.2.
I have Ambari 2.5 setup, i got the stale alert but when i entered in path /etc/ambari-agent/conf/ambari-agent.ini the default alert_grace_period =10.
So can you please help me to rid of this?
thank you !!!
Created 07-17-2017 10:19 AM
Did you perform a Disable and Enable operation on the stale alert definition from ambari UI. Please wait for 10-15 seconds between disabling and enabling the stale alert to see if it gets cleared.
.
Created 07-17-2017 10:19 AM
Did you perform a Disable and Enable operation on the stale alert definition from ambari UI. Please wait for 10-15 seconds between disabling and enabling the stale alert to see if it gets cleared.
.
Created 07-17-2017 11:10 AM
It worked for now !!!!!!!!! thanks for the support.....
Created on 07-17-2017 11:48 AM - edited 08-18-2019 01:05 AM
Created 07-17-2017 12:00 PM
If all those stale alerts are coming from any particular host then you will need to check the hostname which is causing the stale alert.
# curl -i -H "X-Requested-By: ambari"-u admin:admin -X GET http://AMBARI_SERVER_HOST:8080/api/v1/hosts
.
Please list all the hosts using the above curl command (or by opening the mentioned URL in the browser, Where you have logged in to ambari UI) and then match the hosts list to findout if by mistake any unwanted host is being registered. Some times old host can have the ambari-agent.ini entry to point to ambari server.
.
Created 07-20-2017 08:26 AM
I can see in the ambari ui that Node 4 in my cluster is giving the STALE alert.
I verified the URL registered hosts and Hosts entry on all the nodes it seems perfect.