apache / apache/dubbo

[Bug] Unable to perceive the latest subscription services

Open
#13,854 5 comments 0 reactions 0 assignees View on GitHub
component/sdk help wanted type/bug
Dominant language
Java
Stars
41.6k
Forks
26.4k
Avg merge
15h 13m
Merged PRs (30d)
4

Description

### 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 3.2.12

### Steps to reproduce this issue

![image](https://github.com/apache/dubbo/assets/6240229/562ead58-f6e8-4b30-881e-e1b671de417b)

1. Get two instances here, one of which is about to die.
2. Both instances establish NettyConnectionClient, synchronised connection server appears to wait. At this point one of the instances is offline. The local nacos local cache is already listening for the latest metadata info.
3. Wait for all the NettyConnectionClient to complete, at which point the subscription relationship is done. Unable to trigger

### What you expected to happen

Refreshing the service

### Anything else

_No response_

### Are you willing to submit a pull request to fix on your own?

- [X] 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)

Contributor guide

Open the contributing guide

Research direction

Start by tracing the Java SDK flow involving NettyConnectionClient, the Nacos local cache, and subscription completion in the reported two-instance scenario. Reproduce the case where one instance goes offline while connections are being synchronized, then identify why the latest service metadata does not trigger a refresh. Done means the subscription relationship refreshes when the updated metadata is received.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.