Ambari shows the Zookeeper quorum as down but Zookeeper is running on all quorum nodes. Can I force Ambari to refresh?

[#1]

I want to avoid using the REST API to force the status. And even though the service is marked as down, there is no option to run a service check.

[#2]

You could try to restart the Ambari Agents on the Zookeeper nodes or the complete ambari server. What is the current state of the Zookeeper service and host_components? could you check via Rest API <ambari-server>/api/v1/clusters/<clustername>/services/ZOOKEEPER

[#3]

I pulled the status and everything showed up as started! The Ambari agents and server were then cycled with no change in status.

[#4]

@terry

clear the browser cache and check the status. Please post the log entries from ambari-server.log related to zk.

[#5 · Accepted solution]

The incorrect status was caused by the contents of the zookeeper_server.pid file being out of sync with the running zookeeper process. Updating the file with the proper PID allowed the correct Zookeeper status to be displayed in Ambari.

[#6]

@terry Did you update the pid manually?

[#7]

Sounds like this could be a bug..

[#8]

The PID-file problem is actually quite common. I have seen this a couple of times already, not just zookeeper-related (e.g. services not starting because of existing pid file with invalid process id, ...).

[#9]

@Jonas Straub when you see this behaviour could you make sure to log a ticket with our support team.

FYI, I've asked support to get the ZK issue in a ticket.

[#10]

@Olivier Renault I usually do 🙂