[
https://issues.apache.org/jira/browse/MAPREDUCE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12783971#action_12783971
]
Hong Tang commented on MAPREDUCE-1222:
--------------------------------------
@dick, thanks for the comments. I am combing through the jdk code too and
struggling to find the any explicit API. Finally, I found out that there are
calls to directly translate ipv4/6 addresses from string literal form ot
Inet{4|6}Address objects, but they are not in JDK, instead they are in
sun.net.util.IPAddressUtil - which makes it unusable (unless we mandate
everybody use sun jvm).
What bothers me for re-implementing RFC 2372 (IPv6 address architecture) is
that it is a complicated scheme and we probably need a suite of unit-tests to
guarantee our implementation is correct - which sounds to me to be way beyond
the scope of this jira (which should not even exist if HDFS-778 is fixed).
> [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: IPv6-predicate.patch, 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.
