hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4482) Hadoop JMX usage makes Nagios monitoring impossible
Date Mon, 16 Feb 2009 18:00:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-4482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12674019#action_12674019
] 

Tom White commented on HADOOP-4482:
-----------------------------------

The change is tested by existing unit tests so it doesn't new tests (but see also HADOOP-5237).

> Hadoop JMX usage makes Nagios monitoring impossible
> ---------------------------------------------------
>
>                 Key: HADOOP-4482
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4482
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: metrics
>    Affects Versions: 0.18.1
>            Reporter: Brian Bockelman
>            Assignee: Brian Bockelman
>             Fix For: 0.19.1, 0.20.0
>
>         Attachments: hadoop-4482.patch, jmx_name.patch, jmx_name_replaced.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message