2.7.15 重启服务消费者,会无法找到服务提供者,需要再次重启服务提供者,2.7.8 不存在这个问题
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
dubbo-spring-boot-starter 2.7.15
springboot 2.3.2.RELEASE
使用nacos 2.0.3 / 1.4.1 作为注册中心
依次启动服务提供者和消费者,能正常调用,当重启服务消费者,调用会报无法找到服务提供者 org.apache.dubbo.rpc.RpcException: No provider available from registry xxxxx:80 for service ....... 再重启服务提供者,则恢复正常
配置
```
# Dubbo
dubbo:
scan:
# dubbo 服务扫描基准包
base-packages: com.xxxx.xxxx.item.service
# 协议
protocols:
# dubbo 协议
dubbo:
name: dubbo
port: -1
registry:
address: nacos://xxxxx:80/?username=nacos&password=nacos&namespace=${spring.profiles.active}&group=ARK_SAILOR
application:
qos-enable: false
logger: slf4j
consumer:
check: false
```
Contributor guide
Research direction
Reproduce the startup sequence with dubbo-spring-boot-starter 2.7.15, Spring Boot 2.3.2.RELEASE, and Nacos 2.0.3 or 1.4.1 using the configuration shown. Compare the behavior with 2.7.8 and trace provider discovery after restarting only the consumer. Done means the consumer can find and call the provider again without restarting the provider.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100