[
https://issues.apache.org/jira/browse/MAPREDUCE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12782037#action_12782037
]
Dick King commented on MAPREDUCE-1222:
--------------------------------------
1: Should we worry about IPV6 numeric addresses? I'll write the regex if you
want.
2: Proposed line 249 of {{SimulatorEngine.java}} reads:
{{// ips and as host names. We remove them from the parsed network topology}}
and should read
{{// ips [as opposed to host names]. We remove numeric ips from the parsed
network topology}}
The former wording implies that we remove _both forms_ of a doubled address.
3: Do we mean to make {{isIPAddress}} part of the package local API?
3a: If not, testing {{isIPAddress}} should be accomplished by making the
addresses that superficially look like IPs but aren't part of the test case in
{{topo-with-numeric-ips.json}} .
> [Mumak] We should not include nodes with numeric ips in cluster topology.
> -------------------------------------------------------------------------
>
> Key: MAPREDUCE-1222
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1222
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: contrib/mumak
> Affects Versions: 0.21.0, 0.22.0
> Reporter: Hong Tang
> Assignee: Hong Tang
> Fix For: 0.21.0, 0.22.0
>
> Attachments: mapreduce-1222-20091119.patch,
> mapreduce-1222-20091121.patch
>
>
> Rumen infers cluster topology by parsing input split locations from job
> history logs. Due to HDFS-778, a cluster node may appear both as a numeric ip
> or as a host name in job history logs. We should exclude nodes appeared as
> numeric ips in cluster toplogy when we run mumak until a solution is found so
> that numeric ips would never appear in input split locations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
