As for monitoring, we prefer to instrument Zookeeper with an additional thread that periodically reports into our monitoring framework. This way, we don't have to rely on the slightly strange security models of JMX, but can handle any protocol necessary. It also does not require JMX ports to be exposed through firewalls shielding the Zookeeper ensemble from the rest of the world - including the monitoring sites. JMX would only be used for ad-hoc inspections of run-time parameters. Well, I guess it is a somewhat religious issue whether to use JMX or not.
Thanks Jürgen! We'll make use of that in SPM <http://sematext.com/spm/>, thanks. I see Ani (hi!) replied with info about 4 char commands, which we could also use, but if you think about apps that already connect to ZK JMX (think of this as an API) to gather info about ZK, it might be cleaner to expose the version via JMX, too, so they don't have to have logic/code for connecting to ZK JMX to get things like metrics, and then also connect another way to run this one ZK command that grabs the version info. Otis -- Monitoring * Alerting * Anomaly Detection * Centralized Log Management Solr & Elasticsearch Support * http://sematext.com/ On Wed, Nov 12, 2014 at 5:01 PM, "Jürgen Wagner (DVT)" < email@example.com> wrote:Hello Otis, you can try this via echo mntr | nc localhost 2181 or within a Java program including the Zookeeper libraries, there is String org.apache.zookeeper.Version.getVersion() and some other version-relevated methods in this class. Best regards, --Jürgen
Mit freundlichen Grüßen/Kind regards/Cordialement
i.A. Jürgen Wagner
Head of Competence Center "Intelligence"
& Senior Cloud Consultant