-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Support specified naming UDP push port for client #5439
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use nacos code style to reformat code.
代码格式修正了 |
请问,在一个机器上 存在多个nacos client 怎么办????大佬跪舔 。希望快速回复,等着上线。 |
您那边怎么设置的push.receiver.udp.port |
设置在jvm中, -Dpush.receiver.udp.port=10086 |
您好,我们开始也想着在jvm中设置 这种方式还支持一个机器上存在多个nacos client ,因为env设置的环境变量,仅仅在
|
nacos+dubbo 以consumer端部署的时候如果部署在容器内(docker内).就会发现provider list 的更新频率变成自动跑的任务的更新频率,而且永远收不到udp的push信息,这是因为docker内部安装的应用需要提前通知他们使用什么端口,不然其实是隔离的(比如桥接模式).
简单描述就是:查询list列表的时候会上报udp端口,但nacos server 获取到变更后并不能通知到容器中 dubbo 的 consumer端