[jira] Resolved: (CASSANDRA-628) java.net.SocketException: Invalid argument / java.net.NoRouteToHostException: Network is unreachable

["Eric Evans (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Evans resolved CASSANDRA-628.
----------------------------------

       Resolution: Fixed
    Fix Version/s:     (was: 0.7.1)
                   0.7 beta 3

committed.

> java.net.SocketException: Invalid argument / java.net.NoRouteToHostException: Network is unreachable
> ----------------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-628
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-628
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.6.6, 0.7 beta 3
>         Environment: Linux, FreeBSD, (possibly others)
>            Reporter: Eric Evans
>            Assignee: Eric Evans
>             Fix For: 0.7 beta 3
>
>
> This manifests as either a SocketException that occurs when starting a cassandra node, or a NoRouteToHostException which occurs when connecting with a client.
> On Linux systems this is caused by IPV6_V6ONLY being set true. The docs (ipv6(7)) say that when set this causes sockets to be created IPv6 only, while the previous behavior also allowed sending and receiving packets using an  IPv4-mapped IPv6 address.
> The quick fix is to either launch applications using the -Djava.net.preferIPv4Stack=true property, or on Linux systems set net.ipv6.bindv6only=0 (see sysctl(8)).
> My limited understanding is that the previous behavior (IPV6_V6ONLY=0) was always considered a hack to be used until IPv6 was more mature/had gained traction and that a change in defaults was always inevitable, so in the long-term a Real Fix will be needed.
> http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6342561
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560056

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.