Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <18600480.1216617931629.JavaMail.jira@brutus>
Date: Sun, 20 Jul 2008 22:25:31 -0700 (PDT)
From: "Amar Kamat (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Updated: (HADOOP-3780) JobTracker should synchronously
 resolve the tasktracker's network location when the tracker registers
In-Reply-To: <1587220438.1216289131951.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-3780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Amar Kamat updated HADOOP-3780:
-------------------------------

    Attachment:     (was: HADOOP-3245-v4.2.patch)

> JobTracker should synchronously resolve the tasktracker's network location when the tracker registers
> -----------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-3780
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3780
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: mapred
>            Reporter: Amar Kamat
>         Attachments: HADOOP-3780-v1.1.patch, HADOOP-3780-v1.patch
>
>
> This issue is inspired by HADOOP-3620. In JobTracker, the network address of tracker gets resolved asynchronously. Now it can be done inline i.e while the trackers register. This is of great help for HADOOP-3245 where this enhancement makes the design simpler.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.