hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12122) Fix Hadoop should avoid unsafe split and append on fields that might be IPv6 literals
Date Tue, 13 Oct 2015 20:03:05 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14955537#comment-14955537

Colin Patrick McCabe commented on HADOOP-12122:

NoSuchMethodError and ClassNotFound happened sometimes in our jenkins because of a race condition
when multiple maven instances modified the .m2 directory and stomped on each other. See http://mail-archives.apache.org/mod_mbox/hadoop-common-dev/201509.mbox/%3CCAGB5D2YfADn0umyLNrYpO-t4_c88Y4r8QdFRem7pgjTe8SSJog@mail.gmail.com%3E
for a discussion.  This is supposed to be fixed by the Dockerization stuff in Yetus, so hopefully
it won't re-occur.

> Fix Hadoop should avoid unsafe split and append on fields that might be IPv6 literals
> -------------------------------------------------------------------------------------
>                 Key: HADOOP-12122
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12122
>             Project: Hadoop Common
>          Issue Type: Sub-task
>    Affects Versions: HADOOP-11890
>            Reporter: Nate Edel
>            Assignee: Nemanja Matkovic
>         Attachments: HADOOP-12122-HADOOP-11890.0.patch, HADOOP-12122-HADOOP-11890.3.patch,
HADOOP-12122-HADOOP-11890.4.patch, HADOOP-12122-HADOOP-11890.5.patch, HADOOP-12122-HADOOP-12122.2.patch,
HADOOP-12122-HADOOP-12122.3.patch, HADOOP-12122.0.patch, lets_blow_up_a_lot_of_tests.patch
> There are a fairly extensive number of locations found via code inspection which use
unsafe methods of handling addresses in a dual-stack or IPv6-only world:
> - splits on the first ":" assuming that delimits a host from a port
> - produces a host port pair by appending :port blindly (Java prefers [ipv6]:port which
is the standard for IPv6 URIs)
> - depends on the behavior of InetSocketAddress.toString() which produces the above.
> This patch fixes those metaphors that I can find above, and replaces calls to InetSocketAddress.toString()
with a wrapper that properly brackets the IPv6 address if there is one.

This message was sent by Atlassian JIRA

View raw message