Uploaded image for project: 'Hadoop HDFS'
  1. Hadoop HDFS
  2. HDFS-412

Hadoop JMX usage makes Nagios monitoring impossible

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.21.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed

      Description

      When Hadoop reports Datanode information to JMX, the bean uses the name "DataNode-" + storageid. The storage ID incorporates a random number and is unpredictable.

      This prevents me from monitoring DFS datanodes through Hadoop using the JMX interface; in order to do that, you must be able to specify the bean name on the command line.

      The fix is simple, patch will be coming momentarily. However, there was probably a reason for making the datanodes all unique names which I'm unaware of, so it'd be nice to hear from the metrics maintainer.

        Attachments

        1. hadoop-4482.patch
          3 kB
          Thomas White
        2. hdfs-412.patch
          3 kB
          Thomas White
        3. jmx_name_replaced.patch
          0.7 kB
          Brian Bockelman
        4. jmx_name.patch
          0.7 kB
          Brian Bockelman

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. HADOOP-4520 javax.management.MalformedObjectNameException: Invalid character ':' in value part of property

          • Blocker - Blocks development and/or testing work, production could not run
          • Closed

            Activity

              People

              • Assignee:
                bockelman Brian Bockelman
                Reporter:
                bockelman Brian Bockelman
              • Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: