You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2012/05/08 23:15:48 UTC

[jira] [Updated] (HADOOP-8304) DNSToSwitchMapping should add interface to resolve individual host besides a list of host

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

Eli Collins updated HADOOP-8304:
--------------------------------

    Resolution: Not A Problem
        Status: Resolved  (was: Patch Available)

Cool, closing this one as won't fix.  Thanks for filing a separate jira, please link it in here.
                
> 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