[
https://issues.apache.org/jira/browse/MAPREDUCE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12789032#action_12789032
]
Hong Tang commented on MAPREDUCE-1222:
--------------------------------------
Ok, I did a bit research, and (with some help from Hairong) found out that the
numeric ip string is obtained by NN when a DN registers itself with NN through
o.a.h.ipc.Server.getRemoteIAddress(), which in turn calls
InetAddress.getHostAddress() to get the string representation of the ip
address. For an Inet6Address, the format would always be 8 hexadecimal numbers
(in the range from 0 to ffff) separated by ":" (each number may be represented
by 1 to 4 hexadecimal characters).
So for this jira, I'd like to just have a simple regex to recognize this format
instead of arbitrary ipv6 representations.
> [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.
