You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Hairong Kuang (JIRA)" <ji...@apache.org> on 2008/08/05 01:36:44 UTC
[jira] Commented: (HADOOP-3620) Namenode should synchronously
resolve a datanode's network location when the datanode registers
[ https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619741#action_12619741 ]
Hairong Kuang commented on HADOOP-3620:
---------------------------------------
I've just committed this.
> 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.