Skip to content
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

[Bug] dubbo is used with nacos, but there is always “No provider available from registry error” #15040

Open
4 tasks done
17998384 opened this issue Jan 7, 2025 · 1 comment
Labels
component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage

Comments

@17998384
Copy link

17998384 commented Jan 7, 2025

Pre-check

  • I am sure that all the content I provide is in English.

Search before asking

  • I had searched in the issues and found no similar issues.

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

Dubbo java 3.2.4,nacos-client 2.2.4

Steps to reproduce this issue

When both the provider and consumer are restarted simultaneously, and consumer.check = false is set, there is a certain probability that this issue will occur. Upon inspection, the heartbeat connections between the provider and consumer to Nacos appear normal.

What you expected to happen

I suspect that Dubbo's internal service address cache has an issue; it does not replace the local cache with the latest address fetched from Nacos.

Anything else

No response

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

@17998384 17998384 added component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage labels Jan 7, 2025
@AlbumenJ
Copy link
Member

Please try use the latest version of 3.2.x. Service Directory has been fixed for serval times.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/need-triage Need maintainers to triage type/need-triage Need maintainers to triage
Projects
Status: Todo
Development

No branches or pull requests

2 participants