You are welcome Martjin! Glad to have been able to help (
Best,
-Razi
On 4/13/17, 12:13 PM, "Martijn Pieters" <mjpiet...@fb.com> wrote:
On 13/04/2017, 15:06, "Khaja, Raziuddin (NIH/NLM/NCBI) [C]"
<raziuddin.kh...@nih.gov> wrote:
> Looking at your original message:
https://urldefense.proofpoint.com/v2/url?u=http-3A__www.mail-2Darchive.com_user-40cassandra.apache.org_msg51736.html&d=DwIGaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=xmrhtBIDZ_UcilJaq1SH8Q&m=pRFNVjsQoNpE4xWTky8s9kt-twcOChSSvnvSDW6jrfc&s=R0lHgyuqfgHkYPRDYmCpEWN1Q02x5moqZa25mRLdJ80&e=
>
> I see you edited etc/cassandra/cassandra-env.sh, by changing:
>
>
> +#JVM_OPTS="$JVM_OPTS -Djava.net.preferIPv4Stack=true"
>
> +JVM_OPTS="$JVM_OPTS -Djava.net.preferIPv6Addresses=true"
>
> First, I don’t think there is an option java.net.preferIPv6Addresses,
so I would recommend removing that line.
The option does exist, see
https://docs.oracle.com/javase/8/docs/api/java/net/doc-files/net-properties.html.
I had tried both with and without the IPv6 option.
> Second, I believe that starting in apache-cassandra-3.2, that
enabling/disabling the option has been moved to a file called *jvm.options*
[snip evidence of the option moving]
> My guess right now is that you may have upgraded Cassandra from a version
older that 3.1 and somehow your config files are not compatible with 3.10?
**BINGO**. Indeed, I had at some point downgraded to a different Cassandra
version in an attempt to resolve issues with `cqlsh` (which hardcodes a CQL
version). As a result the option was being applied **twice**, in
/etc/cassandra/cassandra-env.sh and via /etc/cassandra/jvm.options.
Removing the switch from both locations now lets Cassandra bind to IPv6.
I now can finally drop the SSH tunnel forwarding the port in my test
cluster.
Thanks!
