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

Hadoop JMX usage makes Nagios monitoring impossible

VotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 0.21.0
    • None
    • None
    • 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

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

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

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment