[
https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624689#action_12624689
]
Hudson commented on HADOOP-3620:
--------------------------------
Integrated in Hadoop-trunk #581 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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,
> netResolution5.patch, netResolution6.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.
