apache / apache/dubbo

关于provider端用新容器滚动发布,产生Connection refused的问题

Open
#12,197 7 comments 0 reactions 0 assignees View on GitHub
status/waiting-for-feedback
Dominant language
Java
Stars
41.6k
Forks
26.4k
Avg merge
15h 13m
Merged PRs (30d)
4

Description

我们公司每次发布成功之后,容器都会有一个新的ip地址。 发布过程是滚动发布的,也就是说在全部应用发布完成之后,provider端的ip都会全部更换一遍。
目前在发布过程中遇到了Connection refused的异常。 查到相关issue:https://github.com/apache/dubbo/issues/9965。 其中讲到这种推空只在所有地址都下线的极端情况下才会出现,对于正常的线上集群实践应该不会出现。 那我这种滚动发布后容器获得新的ip算是应用全部下线的情况吗?

Contributor guide

Open the contributing guide

Research direction

No source file or test is named. Start by reading the linked issue #9965 and trace how provider addresses change during the reported rolling deployment; determine whether the observed Connection refused matches the all-addresses-offline case and document the confirmed behavior or reproduction details.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, distributed-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.