hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hairong Kuang (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3620) Namenode should synchronously resolve a datanode's network location when the datanode registers
Date Mon, 21 Jul 2008 18:17:31 GMT

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

Hairong Kuang commented on HADOOP-3620:
---------------------------------------

> Does the above work?
I thought about this solution too. But if you look at the registration code, sometimes there
is no need to resolve a node's network location if the node has already registered. So network
resolution in the front could be an overhead.

> Note that pre-resolving hosts in include file might not help start up.
Pre-resolving should help since it resolves network locations in batch and therefore reducing
the number of calls to the rack script dramatically.

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


Mime
View raw message