Page History

...

Without monitoring troubleshooting will be more difficult, but not impossible. JMX can be used through jconsole, or access the stats through the four letter words, also the log4j log contains much important/useful information.
You can also use SPM for ZooKeeper to see all ZooKeeper, JVM, and system/host metrics.

Troubleshooting Checklist

...

gchisto is a useful tool for analyzing GC logs https://gchisto.dev.java.net/^{Image Removed}

Additionally you can use 'jstat' on a running jvm to gain more insight into realtime GC activity, see: http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstat.html^{Image Removed}

This issue can be resolved in a few ways:

...

• Verify that logging isn't at DEBUG.Check your log4j.properties file and change the line log4j.rootLogger=DEBUG, ROLLINGFILE to log4j.rootLogger=WARN ROLLINGFILE. Logging to disk on every action can greatly effect performance.
• Verify that you are using fast local disk for the journal.
• Test with http://github.com/phunt/zk-smoketest^{Image Removed}. This should identify real performance along latency issues. It is built against 32 bit python.