Return-Path: 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 920D0905C for ; Tue, 8 May 2012 16:40:10 +0000 (UTC) Received: (qmail 77592 invoked by uid 500); 8 May 2012 16:40:09 -0000 Delivered-To: apmail-hadoop-common-issues-archive@hadoop.apache.org Received: (qmail 77535 invoked by uid 500); 8 May 2012 16:40:09 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-issues@hadoop.apache.org Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 77523 invoked by uid 99); 8 May 2012 16:40:09 -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:40:09 +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:40:08 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 856C743A663 for ; Tue, 8 May 2012 16:39:48 +0000 (UTC) Date: Tue, 8 May 2012 16:39:48 +0000 (UTC) From: "Eli Collins (JIRA)" To: common-issues@hadoop.apache.org Message-ID: <1585335260.39478.1336495188548.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=13270586#comment-13270586 ] Eli Collins commented on HADOOP-8304: ------------------------------------- bq. Do you see any scenario to resolve a list of host? (not counting the unit test) DatanodeManager does that today with a list obtained from the hosts files. bq. I don't understand the question of last comment there as I just want to fix the interface here You mentioned earlier "identify a potential bug that a hostname start with number may not been resolved properly" - doesn't that issue still need to be addressed? > 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 resolve(List 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