Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-7507

jvm metrics all use the same namespace



    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 0.20.2
    • 0.23.0, 0.24.0
    • metrics
    • None
    • Incompatible change, Reviewed
    • JVM metrics published to Ganglia now include the process name as part of the gmetric name.


      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.


        1. ASF.LICENSE.NOT.GRANTED--screenshot-1.jpg
          167 kB
          Jeff Bean
        2. HADOOP-7507v1.patch
          2 kB
          Alejandro Abdelnur
        3. HADOOP-7507-v2.patch
          2 kB
          Michael Katzenellenbogen
        4. HADOOP-7507v3.patch
          2 kB
          Alejandro Abdelnur
        5. HADOOP-7507v4.patch
          3 kB
          Alejandro Abdelnur
        6. HADOOP-7507v5.patch
          3 kB
          Alejandro Abdelnur
        7. HADOOP-7507v6.patch
          9 kB
          Alejandro Abdelnur
        8. HADOOP-7507v7.patch
          9 kB
          Alejandro Abdelnur
        9. hadoop-metrics.properties
          2 kB
          Jeff Bean
        10. JvmMetrics.java
          7 kB
          Jeff Bean



            tucu00 Alejandro Abdelnur
            jwfbean Jeff Bean
            0 Vote for this issue
            7 Start watching this issue