dubbo revision error no provider available
- Dominant language
- Java
- Stars
- 41.6k
- Forks
- 26.4k
- Avg merge
- 15h 13m
- Merged PRs (30d)
- 4
Description
我们使用dubbo 2.7.13 注册中心为nacos 启动消费者报找不到provider错误
之前配置类似为
```
@DubboReference(version = "${dubbo.version}", parameters = {"timeout", "${dubbo.timeout}"})
```
消费者启动报provider找不到
排查发现注册中心上consumer的配置revision莫名其妙的为所引用的rpc包的版本号
类似```release=2.7.13&retries=0&revision=1.1.0-RELEASE&```
其中1.1.0-RELEASE并不是我们在配置文件中配置的dubbo版本号,反而是依赖二方包的版本号
改为
```
@DubboReference(version = "${dubbo.version}", parameters = {"timeout", "${dubbo.timeout}","revision","${dubbo.version}"})
```
即可
一共有三个消费者,只有一个消费者报错,其他消费者也都没有配置revision,却没有报错,很奇怪
Contributor guide
Research direction
Start with the @DubboReference configuration and reproduce consumer startup on Dubbo 2.7.13 with Nacos, comparing the revision metadata from all three consumers. Investigate why one consumer derives revision=1.1.0-RELEASE from a dependent RPC package; done means provider discovery succeeds without manually adding revision and the revision metadata is consistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend-api-design, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100