[
https://issues.apache.org/jira/browse/HADOOP-8928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13503495#comment-13503495
]
Steve Loughran commented on HADOOP-8928:
----------------------------------------
I agree with the need to do topology reset, and like what you've done client
side.
Server side, the reset operation ought to go into the new topology base class,
with a helper method there to attempt a reset. I don't want any hard-coded
{{instanceof CachedDNSSwitchTopology}} checks in the source -removing the
existing one is a goal.
Testing this stuff should be straightforward: minidfs cluster to have its topo
reset; use the dump topology information to assess its before/after state.
> Add ability to reset topologies on master nodes
> -----------------------------------------------
>
> Key: HADOOP-8928
> URL: https://issues.apache.org/jira/browse/HADOOP-8928
> Project: Hadoop Common
> Issue Type: Improvement
> Components: net
> Affects Versions: 3.0.0, 2.0.2-alpha
> Reporter: Shinichi Yamashita
> Attachments: HADOOP-8928.txt
>
>
> For a topology decision of DataNode and TaskTracker, ScriptBasedMapping
> (probably TableMapping) confirms HashMap first.
> To decide topology of DataNode and TaskTracker again, it is necessary to
> restart NameNode and JobTracker.
> Therefore, it is necessary to change (or clear) HashMap function without
> restarting NameNode and JobTracker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
