dubbo3的instance模式下Protobuf (IDL) + Triple的bug问题
- Dominant language
- CSS
- Stars
- 491
- Forks
- 809
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 6
Description
dubbo3,将服务改成instance模式后,消费者端在调用服务者端时找不到provider,接口名对应,组名版本都是对应的,服务通信正常的。
简单的概括就是:所有一样的情况下,只改了服务端的注册模式,在all时运行正常,在instance时出现服务发现失败?,补充一下,仅仅是在tri协议下的instance模式的Protobuf (IDL) + Triple风格调用的情况下才有此问题,普通java Interface + Triple 协议的风格调用的模式是正常的。
再简单概括就是:instance模式,tri协议,Protobuf (IDL) + Triple风格,三个都限定的条件下才不行
服务端:

消费端:

就是想问一下是为什么还是说确实是bug
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the service-discovery failure under the three stated conditions: instance mode, the tri protocol, and Protobuf (IDL) with Triple-style calls. Compare it with all registration mode and ordinary Java interface calls, which reportedly work. Done means identifying the cause and confirming whether this is a bug; the issue names no files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100