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] Updated: (HADOOP-3620) Namenode should synchronously resolve a datanode's network location when the datanode registers
Date Tue, 24 Jun 2008 00:17:44 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Hairong Kuang updated HADOOP-3620:
----------------------------------

    Attachment: netResolution.patch

Dhruba's comment makes sense. The attached inital patch still let the thread hold the global
lock while resolving a network location. I need to figure out how not to hod the lock without
any risk of data structure inconsistency.

The attached patch resolves a data node's network location when it registers. It also lets
a data node to randomly back off its block report when the data node starts up.

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