Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <196644150.1214288265206.JavaMail.jira@brutus>
Date: Mon, 23 Jun 2008 23:17:45 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-3620) Namenode should synchronously
 resolve a datanode's network location when the datanode registers
In-Reply-To: <342581703.1214245125137.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Amar Kamat commented on HADOOP-3620:
------------------------------------

I think it also makes sense to do the same in the JobTracker. There too the resolution is async. With HADOOP-3590 getting fixed, the problem is that the tasks will be scheduled randomly until the node gets resolved. Some of the test cases assume that the all the TTs are resolved before the job gets submitted which might not be true always. Thoughts?

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