Return-Path: 
 <common-issues-return-31047-apmail-hadoop-common-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-common-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 689AC9191
	for <apmail-hadoop-common-issues-archive@minotaur.apache.org>;
 Tue,  8 May 2012 16:56:11 +0000 (UTC)
Received: (qmail 32860 invoked by uid 500); 8 May 2012 16:56:10 -0000
Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org
Received: (qmail 32785 invoked by uid 500); 8 May 2012 16:56:10 -0000
Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:common-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:common-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:common-issues@hadoop.apache.org>
List-Id: <common-issues.hadoop.apache.org>
Reply-To: common-issues@hadoop.apache.org
Delivered-To: mailing list common-issues@hadoop.apache.org
Received: (qmail 32678 invoked by uid 99); 8 May 2012 16:56:10 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 16:56:10 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 May 2012 16:56:09 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id BE18743AFF4
	for <common-issues@hadoop.apache.org>; Tue,  8 May 2012 16:55:49 +0000 (UTC)
Date: Tue, 8 May 2012 16:55:49 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <196984772.39586.1336496149779.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2058263656.4388.1335177455679.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8304) DNSToSwitchMapping should add
 interface to resolve individual host besides a list of host
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Junping Du commented on HADOOP-8304:
------------------------------------

That's for caching only. If you think list interface here is good, I agree that it may be better to leave it there which will not take complexity of incompatibility. 
About the bug that wrongly resolve the hostname starting with number, yes. I will go ahead to file a jira and it could be easy to fix it.

                
> DNSToSwitchMapping should add interface to resolve individual host besides a list of host
> -----------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8304
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8304
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: io
>    Affects Versions: 1.0.0, 2.0.0
>            Reporter: Junping Du
>            Assignee: Junping Du
>             Fix For: 2.0.0
>
>         Attachments: HADOOP-8304-V2.patch, HADOOP-8304-V2.patch, HADOOP-8304.patch
>
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> DNSToSwitchMapping now has only one API to resolve a host list: public List<String> resolve(List<String> names). But the two major caller: RackResolver.resolve() and DatanodeManager.resolveNetworkLocation() are taking single host name but have to wrapper it to an single entry ArrayList. This is not necessary especially the host has been cached before.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira