Ganglia jvm metrics don't make sense because it's not clear which java process the metrics refer to. In fact, all hadoop java processes running on a node report their jvm metrics to the same namespace.
The metrics are exposed by the "jvm" context in JvmMetrics.java. This leads to confusing and nonsensical graphs in ganglia and maybe other monitoring tools.
One way to fix this is to make sure the process name is reported in the jvm context, making it clear which process is associated with the context, and separating out the jvm metrics per process.
This is marked as an "incompatible change" because the fix provided removes the JVM metrics and replaces it with process-specific metrics.
|Assignee||Alejandro Abdelnur [ tucu00 ]|
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Fix Version/s||0.23.0 [ 12315569 ]|
|Fix Version/s||0.24.0 [ 12317652 ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Hadoop Flags||[Incompatible change]||[Incompatible change, Reviewed]|
|Resolution||Fixed [ 1 ]|
|Release Note||JVM metrics published to Ganglia now include the process name as part of the gmetric name.|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|19d 18h 35m||2||Alejandro Abdelnur||01/Sep/11 20:00|
|10d 9h 54m||3||Alejandro Abdelnur||02/Sep/11 22:48|
|5d 1h 11m||1||Todd Lipcon||08/Sep/11 00:00|
|68d 1h 50m||1||Arun C Murthy||15/Nov/11 00:50|