hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3620) Namenode should synchronously resolve a datanode's network location when the datanode registers
Date Fri, 27 Jun 2008 12:52:45 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608759#action_12608759
] 

Devaraj Das commented on HADOOP-3620:
-------------------------------------

I haven't gone through the patch in detail but one thing which struck me is that you removed
the cache from ScriptBasedMapping and moved it to the dfs part of the framework. That might
be a problem for MR part of the framework.

> 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
>
>
> 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.


Mime
View raw message