New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement IPv6 support for distributed XGBoost #7725
Comments
Hi @ikriv , thank you for raising the issue. Would you like to work on this? |
@trivialfis I am also interested in this issue, could you point where we should start? |
I will take a deeper look into this. |
Hi. It's a possibility, but I can't fully commit right now :) That is, if someone else volunteers, I would be very grateful. |
I will try to implement it after 1.6. Note to myself:
|
Thank you so much, @trivialfis! I think Python tracker is already good (at least it does not complain loudly), it's the socket wrapper that insists on IPv4 |
Thanks for including this in 2.0 roadmap! |
Not yet. I will update this thread. |
Hi, can anyone here help with providing guidance on testing IPv6 on a public cloud like AWS or GCP? I'm not an expert on network administrating and got lost in those cloud documents. The draft PR is here: #8225 . |
I tested the code using GCP VM instances. Feel free to try it if you are interested in this. |
Q: I noticed the ipv6 support is on the 2.0 Roadmap. is there any plan or date for ipv6 support on pyspark :) |
Would be great if there people with expertise can help work on this. It takes some effort to setup a test environment in the CI and we don't have any admin. |
Is spark ipv6 supported now? If not I'd like to contribute. |
Currently distributed XGBoost does not support IPv6, this is explicitly asserted in rabit/include/rabit/internal/socket.h
Our internal network is IPv6 only, which means we can't run XGBoost out of the box.
IPv6 is 20+ years old, and IPv4 is being phased out more and more as the time progresses. I think it is very important to enable IPv6 in XGBoost for more successful adoption.
The text was updated successfully, but these errors were encountered: