[
https://issues.apache.org/jira/browse/HDFS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom White updated HDFS-412:
---------------------------
Fix Version/s: 0.21.0
Status: Patch Available (was: Open)
Re-submitting to Hudson.
> Hadoop JMX usage makes Nagios monitoring impossible
> ---------------------------------------------------
>
> Key: HDFS-412
> URL: https://issues.apache.org/jira/browse/HDFS-412
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Brian Bockelman
> Assignee: Brian Bockelman
> Fix For: 0.21.0
>
> Attachments: hadoop-4482.patch, hdfs-412.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.
