Dubbo Java 2.7.1 occasionally problem. When the provider of dubbo deploying, and the IP is changed. The new provider's IP has been pushed to dubbo, but the error shows that the consumer still sends requests to the old IP that has been offline.

[Wide-wide]

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 Iava 2.7.1

Steps to reproduce this issue

Our self-developed registration and discovery service relies on dubbo. During the release of the provider by the business side, their IPs changed. According to the dubbo 2.7.1 log tracking, the new provider's IP has been pushed to dubbo. Accoring to dubbo source cod log: logger.info("Notify urls for subscribe url " + url + ", urls: " + urls); Providers' ip typed out is correct.

However, this problem is sporadic. We tried to reproduce it many times locally but failed. The business side encountered this problem twice. The consumer failed to call the provider, and one of them was restored half an hour later,the consumer reconnected to the correct provider.

What you expected to happen

Normally, we push the correct provider IP to dubbo, then dubbo should push the correct provider IP to the consumer, and the consumer will establish a connection to the new provider.I hope to find out the cause of this BUG in Dubbo Java 2.7.1 and which version has fixed this problem.

Anything else

Occasional problem, difficult to reproduce

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

• I agree to follow this project's Code of Conduct

[AlbumenJ]

Please try on the latest version. For this problem, we have fixed several times for diferent scenarios.

[Wide-wide]

Please try on the latest version. For this problem, we have fixed several times for diferent scenarios.

It is difficult for the business side to upgrade the version. Do you have a detailed explanation about this problem? We want to fix and reproduce this problem in 2.7.1

[AlbumenJ]

Please try on the latest version. For this problem, we have fixed several times for diferent scenarios.

It is difficult for the business side to upgrade the version. Do you have a detailed explanation about this problem? We want to fix and reproduce this problem in 2.7.1

We have fixed it for more that 5 times and it is really hard to figure all of them out.