英文:
Why Ignite TcpClientChannel port can not larger than 49151?
问题
Background: 我想使用testcontainers来进行与Apache Ignite的单元测试。
我目前正在使用Ignite客户端，并在Docker的端口映射功能的上下文中遇到了一个潜在问题。
在Docker中，端口映射涉及随机分配端口，这往往会超出Ignite客户端中的TcpClientChannel似乎可允许的范围。
是否有人可以提供一些关于为什么TcpClientChannel存在这些限制的见解？此外，在涉及Docker的情况下，应该如何管理端口映射是常见需求的情况，以考虑这些限制？
感谢您的时间和帮助。
英文:
Background: I want to use testcontainers to do unit tests with apache ignite
I am currently working with the Ignite client and have come across a potential issue with its port restrictions, specifically in the context of Docker's port mapping feature.
In Docker, port mapping involves randomly assigning ports, which can quite often exceed the range that seems to be permissible by the TcpClientChannel in the Ignite client.
Can anyone provide some insight into why these limitations exist within the TcpClientChannel? Additionally, how should we manage scenarios involving Docker, where port mapping is a common necessity, in light of these restrictions?
Thank you for your time and assistance.
答案1
得分: 2
1024 - 49151 被称为注册端口范围。
然而，Ignite客户端中的限制毫无意义。我已经提交了一个工单并开始了讨论：https://issues.apache.org/jira/browse/IGNITE-20026。
英文:
1024 - 49151 is so-called registered port range.
However, the limitation in Ignite client does not make sense. I've filed a ticket and started a discussion: https://issues.apache.org/jira/browse/IGNITE-20026
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论