[
https://issues.apache.org/jira/browse/ZOOKEEPER-2424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15281037#comment-15281037
]
Andrew Purtell commented on ZOOKEEPER-2424:
-------------------------------------------
FWIW, HBase picked up Hadoop's JvmPauseMonitor and also hooked it up to
metrics:
https://github.com/apache/hbase/blob/branch-1/hbase-server/src/main/java/org/apache/hadoop/hbase/util/JvmPauseMonitor.java
. The metrics system here is HBase's, and is convoluted because we build on
Hadoop metrics, have to support multiple versions of Hadoop, and also export to
JMX. I'd imagine you'd make a similar modification but just export to JMX as
done elsewhere in ZK.
> Detect and log possible GC churn in servers.
> --------------------------------------------
>
> Key: ZOOKEEPER-2424
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2424
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Chris Nauroth
> Labels: newbie
> Fix For: 3.5.3
>
>
> Excessive JVM garbage collection pauses can harm the stability of a ZooKeeper
> ensemble. If a stop-the-world GC pause in a server lasts long enough, then
> the the node will drop out of the ensemble. If this happens on multiple
> nodes simultaneously, then there is a risk of loss of quorum. This issue
> proposes to detect long GC pauses, log warnings about them, and expose
> metrics about them.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
