IGNITE通信SPI支持IPv6
我已经在多个位置阅读了有关IGNITE在IPv6中存在潜在问题的信息，我们在Kubernetes设置中看到了类似的通信问题，而IGNITE的通信SPI似乎随机失败了。
Ignite docs 为了支持IPv4和IPv6，但这有时可能导致群集分离的问题。”
我有两个问题：
- 以上两个来源都非常模糊，还有其他文档详细描述了IPv6通信的问题以及如何解决这些问题（除了使用IPv4之外）吗？
- 从实际的角度来看，可以在纯IPv6环境中点燃功能吗？同样，任何可以支持此答案的文档/来源将不胜感激。
I have read in multiple locations about Ignite having potential issues with IPv6 and we have been seeing similar communication issues within our Kubernetes setup with Ignite, where the communications spi seems to randomly fail.
The Ignite docs state that "Ignite tries to support IPv4 and IPv6 but this can sometimes lead to issues where the cluster becomes detached."
While point 4 of this source states "It can’t be said that Ignite doesn’t support the IPv6 protocol, but at this moment, there are a few specific problems."
I have two questions:
- Both of the above sources are very vague, is there any other documentation that describes in detail the issues with IPv6 communication and how to resolve them (apart from using IPv4)?
- From a practical standpoint, can Ignite function in a purely IPv6 environment? Again any documentation/sources to back this answer up would be appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
问题在于，在许多网络中，IPv6是已启用，但不是配置的，这意味着IGNITE可以看到地址并尝试使用它，但是没有数据路由。
如果您的IPv6网络已正确配置，并且所有节点都可以“看到”彼此，则应起作用。
The problem is that in many networks, IPv6 is enabled but not configured, meaning that Ignite can see the address and tries to use it, but no data is routed.
If your IPv6 network is correctly configured and all the nodes can "see" each other, then it should work.