[
https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614682#action_12614682
]
Hadoop QA commented on HADOOP-3620:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12386366/netResolution4.patch
against trunk revision 677839.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
+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 passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2899/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2899/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2899/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/2899/console
This message is automatically generated.
> Namenode should synchronously resolve a datanode's network location when the
> datanode registers
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-3620
> URL: https://issues.apache.org/jira/browse/HADOOP-3620
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.19.0
>
> Attachments: netResolution.patch, netResolution1.patch,
> netResolution2.patch, netResolution3.patch, netResolution4.patch
>
>
> Release 0.18.0 removes the rpc timeout. So the namenode is ok to resolve a
> datanode's network location when the datanode registers. This could remove
> quite a lot of unnecessary code in both datanode and namenode to handle
> asynchronous network location resolution and avoid many potential bugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
