kofkyobsa opened a new issue, #15487:
URL: https://github.com/apache/dubbo/issues/15487

   ### Pre-check
   
   - [x] I am sure that all the content I provide is in English.
   
   
   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dubbo/issues?q=is%3Aissue) and found no 
similar issues.
   
   
   ### Apache Dubbo Component
   
   Java SDK (apache/dubbo)
   
   ### Dubbo Version
   
   Dubbo version: 3.3.0
   openjdk:17-jdk-alpine
   Registry: ZooKeeper 
   Orchestration: Kubernetes
   Network: Full connectivity between K8S cluster and ZooKeeper
   
   ### Steps to reproduce this issue
   
   - Deploy Dubbo provider services in K8S cluster, registered to external 
ZooKeeper.
   - Deploy Dubbo consumer services in the same K8S cluster, consuming the 
provider services.
   - Verify that service discovery works correctly and consumers can connect to 
providers.
   - Trigger a redeployment of the provider services in K8S (e.g., rolling 
update).
   - Observe that ZooKeeper registry updates with new provider addresses.
   - Notice that consumers continue attempting to connect to old provider 
addresses, resulting in connection failures.
   
   ### What you expected to happen
   
   When providers are redeployed in K8S and their addresses change in 
ZooKeeper, consumers should:
   Receive offline notifications for old providers.
   Update their provider address caches.
   Establish connections to new providers without errors.
   
   ### Anything else
   
   We are using Dubbo 3.3.0 in a Kubernetes cluster with an external ZooKeeper 
registry. The network connectivity between the K8S cluster and ZooKeeper is 
working properly. However, we are encountering an issue where after redeploying 
provider services in K8S, the ZooKeeper registry correctly updates the provider 
list, but the consumers inside the K8S cluster fail to receive the offline 
notifications for the old providers. This results in connection failures with 
error messages like "Failed to connect to server".
   
   ### Are you willing to submit a pull request to fix on your own?
   
   - [ ] Yes I am willing to submit a pull request on my own!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org
For additional commands, e-mail: notifications-h...@dubbo.apache.org

Reply via email to