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