Can't initialize H2OContext on IPv6-only machine about sparkling-water HOT 10 CLOSED

This can also be reproduced on a dual stack machine by running Spark with -Djava.net.preferIPv6Addresses=true

from sparkling-water.

Thanks @tomdz! We have to improve handling of IPv6 stack in H2O itself.

from sparkling-water.

Any workaround I can use in the meantime ?

from sparkling-water.

So far, i was not able reproduce it, i have dual stack machine, passing:

--conf spark.driver.extraJavaOptions="-Djava.net.preferIPv6Addresses=true"\
--conf spark.executor.extraJavaOptions="-Djava.net.preferIPv6Addresses=true"

I tried to pass different master={local | local[*] | local-cluster[....] }, but creation of H2O context was still successful (but i can see that even spark is using IPV4).

However, i know that inside H2O there are few places expecting IPv4.

from sparkling-water.

Yes, IPv4 is a requirement, and will likely be for the foreseeable future.
Interestingly, I have yet to see an enterprise customer without IPv4.

Tom

On Dec 9, 2015, at 1:30 PM, Michal Malohlava [email protected] wrote:

So far, i was not able reproduce it, i have dual stack machine, passing:

--conf spark.driver.extraJavaOptions="-Djava.net.preferIPv6Addresses=true"
--conf spark.executor.extraJavaOptions="-Djava.net.preferIPv6Addresses=true"
I tried to pass different master={local | local[*] | local-cluster[....] }, but creation of H2O context was still successful (but i can see that even spark is using IPV4).

However, i know that inside H2O there are few places expecting IPv4.

—
Reply to this email directly or view it on GitHub.

from sparkling-water.

We (Facebook) are very heavily invested in IPv6 (see e.g. http://www.internetsociety.org/deploy360/wp-content/uploads/2014/04/WorldIPv6Congress-IPv6_LH-v2.pdf) and software that we run internally is generally required to play nice with IPv6-only hosts these days (which in Java is not all that difficult, fwiw).

from sparkling-water.

@mmalohlava I tried this with Spark 1.5.1 running on JDK 1.8.0_60-b27 on Centos, fwiw. Maybe adding java.net.preferIPv4Stack=false also helps ?

from sparkling-water.

@tomdz so far no luck - java7/java8 with preferIPv4Stack=false uses IPv4. Need to try that on dedicated linux box

from sparkling-water.

Should be fixed now...

from sparkling-water.

HEXDEV-593 https://0xdata.atlassian.net/browse/HEXDEV-593

from sparkling-water.