[
https://issues.apache.org/jira/browse/HADOOP-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-3620:
----------------------------------
Attachment: netResolution3.patch
This patch applies to trunk. Additionally
1. It provides a cached implementation of DNSToSwitchMapping, which caches all
resolved DNS to switch mapping. Any implementation could extend
CachedDNSToSwitchMapping if this helps improve its performance.
2. ScriptBasedMapping is CachedDNSToSwitchMapping while RawScriptBasedMapping
resolves a location only by running a script.
3. Name node pre-resolves the network location of all datanodes in the include
list only if the configured DNSToSwitchMapping is cached.
> Namenode should synchronously resolve a datanode's network location when the
> datanode registers
> -----------------------------------------------------------------------------------------------
>
> Key: HADOOP-3620
> URL: https://issues.apache.org/jira/browse/HADOOP-3620
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs
> Affects Versions: 0.18.0
> Reporter: Hairong Kuang
> Assignee: Hairong Kuang
> Fix For: 0.19.0
>
> Attachments: netResolution.patch, netResolution1.patch,
> netResolution2.patch, netResolution3.patch
>
>
> Release 0.18.0 removes the rpc timeout. So the namenode is ok to resolve a
> datanode's network location when the datanode registers. This could remove
> quite a lot of unnecessary code in both datanode and namenode to handle
> asynchronous network location resolution and avoid many potential bugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
