[
https://issues.apache.org/jira/browse/ZOOKEEPER-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170283#comment-16170283
]
Jon Bringhurst commented on ZOOKEEPER-1281:
-------------------------------------------
{quote}
Is there a workaround for this that people are using when monitoring their
Zookeeper ensemble?
{quote}
We've been using Jolokia (http://jolokia.org) attached to the Zookeeper process
with a Python agent that hits the http endpoint, runs through the
org.apache.ZooKeeperService mbeans, then finally emits various metrics
(including if the server is a participant, leader, or observer) to our
monitoring system. See
https://zookeeper.apache.org/doc/r3.4.6/zookeeperJMX.html to get a
non-exhaustive list of what metrics you can get from Zookeeper's mbeans. This
setup has worked well for monitoring our 80+ Zookeeper clusters for several
years now.
> Stat and srvr 4 letter commands are useless on the leader when leaderServes =
> false
> -----------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-1281
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-1281
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.3.3
> Reporter: Daniel Lord
>
> When leaderServes = false the leader responds to the stat/srvr letter words
> with simply "this ZooKeeper instance is not currently serving requests".
> While I agree that is an accurate statement it's not terribly useful for
> monitoring programs. Additionally, if members of the ensemble are not
> currently in the quorum it becomes impossible to tell who is out of the
> quorum and who is the leader of the quorum.
> I'm not sure if the leader should have a specially formatted response for
> stat/srvr or if it should simply display less information (no connections for
> example).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
