[
https://issues.apache.org/jira/browse/HDFS-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12752128#action_12752128
]
Hadoop QA commented on HDFS-412:
--------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12411401/hdfs-412.patch
against trunk revision 811493.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
-1 core tests. The patch failed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/14/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/14/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/14/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hdfs-Patch-h5.grid.sp2.yahoo.net/14/console
This message is automatically generated.
> 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.
