[
https://issues.apache.org/jira/browse/MAPREDUCE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dick King updated MAPREDUCE-1222:
---------------------------------
Attachment: IPv6-predicate.patch
This is a supplement to the previous patch to expand the regexp to meet the
requirements of RFC 4291 .
The regular expression and the finite state machine that supports it is longer
than it needs to be -- about 2.6K, and probably about 500-1000 nodes in the
FSM. I did it this way to avoid as much backtracking as possible. It seems to
take about 10 microseconds to handle an IPV6 full address, a bit more for an
address with elisions, a bit less for an IPV4 address, and about 5 microseconds
for a non-numeric address.
I'll open the regular expression for comment before I fold it in with the patch
and with other changes I've suggested in the main patch.
> [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.
