Repository navigation
Discussion 2773
- 编号:#2773
- 分类:General
- 状态:已关闭 / 无已采纳答案
- 创建:2025-01-12T13:01:39Z
- 更新:2026-02-13T02:13:08Z
- 作者:No-SilverBullet
社区原始记录;其中的建议、未决提案和版本描述需结合 版本与升级 核对。快照日期:2026-09-20。
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| dubbo-go路由接口的改进 | P1 | #2283 | 文锋 | |
| client can't get attachments which is set from server | P1 | #2641 | ||
| attachment 丢失 | P0 | #2752, #2582 | zhangcunli&文锋&梁嘉嘉 | 嘉嘉尝试复现中 |
| common.URL,、内存、goroutine 泄漏 | P0 | https://github.com/apache/dubbo-go/issues/2722,https://github.com/apache/dubbo-go/issues/2709,https://github.com/apache/dubbo-go/issues/2699, #2683, #2678 | 吴歆帆&罗颖韬 | doc:https://github.com/apache/dubbo-go/discussions/2750,https://github.com/apache/dubbo-go/discussions/2764 跟 歆帆沟通后,推进相关工作。 |
| v3.2 使用问题 | P0 | #2707 #2703 | 文锋 | |
| data race 问题 | P1 | #2277 | 泽亚 | 泽亚能复现,有空解决下 |
| 超时问题改进 | P1 | #2302 | 歆帆 | |
| 接口级别注册时,泛化调用需要请求两次才能正常返回结果 | P2 | #2591 | 凤瑞 | |
| Provides group version support for the reflection service | P1 | #2567 | ||
| 服务治理能力优化 | P1 | #2318 | AlexStocks |
1.triple稳定性,解决之前被识别到的issue
2.triple重构,triple和grpc的关系,一个是基于grpc-go的实现,另外一个基于connect-rpc。
目标基于connect-rpc去做连接管理。
3.内存泄漏问题的定位与解决,需要找一些用户看有没有遇到对应的问题,帮助定位
4.error分类,consumer调用provider过程中可能会出现多种异常,网络异常、序列化异常、server侧、业务异常、http错误码的映射,参考grpc、connect-rpc的error分类。
5.服务发现,了解应用发现、接口发现,确保服务发现机制正常运行,提升稳定性。
6.xDS,proxyless,参考java侧的文档、成果
## RPC Communication
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| 调用java服务端高版本返回的数据过大时报错 | P1 | [#2544](https://github.com/apache/dubbo-go/issues/2544) | ||
| Failed to invoke the method com..*.XxxxService .No provider is available because can't connect server | P1 | [#2607](https://github.com/apache/dubbo-go/issues/2607) | ||
| dubbo-go 调用JAVA-DUBBO 时 moniter 的相关问题 | P1 | [#2431](https://github.com/apache/dubbo-go/issues/2431) |
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| Same address cannot distinguish different registry center | P1 | [#2524](https://github.com/apache/dubbo-go/issues/2524) | ||
| dubbo-go@v3.1.0获取不到nacos配置 | P1 | [#2580](https://github.com/apache/dubbo-go/issues/2580) | ||
| dubbo go与java使用nacos作为注册中心,获取应用metadata的方式不一致导致获取不到provider | P1 | [#2543](https://github.com/apache/dubbo-go/issues/2543) |
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| Rest protocol | P1 | [#2513](https://github.com/apache/dubbo-go/issues/2513) | ||
| dubbo protocol and dubbo-go-hessian2 can not process (*int32)(nil) corner case | P0 | [#2517](https://github.com/apache/dubbo-go/issues/2517) | ||
| the default maxMsgLength for getty param | P1 | [#2619](https://github.com/apache/dubbo-go/issues/2619) | ||
| [Proposal] Unified IDL control for multiple protocols | P1 | [#2595](https://github.com/apache/dubbo-go/issues/2595) |
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| triple 协议 | P0 | [#2263](https://github.com/apache/dubbo-go/issues/2263) | 吴歆帆、方泽亚、史凤瑞、叶凯乐 | 【泽亚+凤瑞】在推进连接池 |
| triple 使用 | P0 | [#2755](https://github.com/apache/dubbo-go/issues/2755) | zhangcunli&歆帆,实际参与人 杨泽睿 | related discussion,[#2756](https://github.com/apache/dubbo-go/discussions/2756) |
| Triple header/trailer usage pattern proposal | P1 | [#2422](https://github.com/apache/dubbo-go/issues/2422) | 这里说明了新 triple 实现的一些细节问题 | |
| 在 Triple 协议下,配置最大消息长度无效 | P1 | [#2487](https://github.com/apache/dubbo-go/issues/2487) | 凯乐 | 正在跟进 |
| Reverse package dependency found: triple is replying on server | P1 | [#2482](https://github.com/apache/dubbo-go/issues/2482) | 泽亚 | 已经解决 |
| protoc-gen-triple 插件与生成代码package路径的讨论 | P1 | [#2475](https://github.com/apache/dubbo-go/issues/2475) | 泽亚 | 已经解决 |
| [DISCUSS] should server package support configuring more RPC features? | P1 | [#2462](https://github.com/apache/dubbo-go/issues/2462) | ||
| Triple non-proto mode support | P2 | [#2491](https://github.com/apache/dubbo-go/issues/2491) | ||
| Move sample code in protocol.triple.internal package to apache/dubbo-go-samples | P1 | [#2498](https://github.com/apache/dubbo-go/issues/2498) | 泽亚 | 跟进中 |
| Triple needs to support register Non-IDL service for backward compatibility | P1 | [#2542](https://github.com/apache/dubbo-go/issues/2542) | 泽亚 | 跟进中 |
| Multi Protocols doesn't work on Nacos | P1 | [#2581](https://github.com/apache/dubbo-go/issues/2581) | 歆帆 | 跟进中 |
| triple request missed http header like scheme, host etc. | P1 | [#2642](https://github.com/apache/dubbo-go/issues/2642) | 歆帆 | 跟进中 |
| 服务调用时 schema 前缀改进 | P1 | https://github.com/apache/dubbo-go/pull/2484,https://github.com/apache/dubbo-go/issues/2488 |
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| [Triple] Add XXX filter automatically when XXX is enabled | P1 | [#2505](https://github.com/apache/dubbo-go/issues/2505) | ||
| dubbo-go 3.2 grafana 大盘 | P1 | [#2520](https://github.com/apache/dubbo-go/issues/2520) | ||
| dubbo v3 版本已经没有这个api设置日志对象的支持 | P1 | [#2526](https://github.com/apache/dubbo-go/issues/2526) | P1 | |
| Triple OpenTelemetry support | P1 | [#2554](https://github.com/apache/dubbo-go/issues/2554) | ||
| 可观测性改进 | P1 | [#2315](https://github.com/apache/dubbo-go/issues/2315) |
| Item | Priority | Issue/Pr | Owner | Description |
|---|---|---|---|---|
| java 转 go的proto工具 | P0 | 何亮、梁嘉嘉、杨泽睿 | dubbo java 海星 已经实现,何亮带着相关筒子继续推进。嘉嘉反馈:等待何亮一些工作完成后继续推进,最近联系不上 何亮。 |
1.triple稳定性,解决之前被识别到的issue
2.triple重构,triple和grpc的关系,一个是基于grpc-go的实现,另外一个基于connect-rpc。
grpc-go更像是一个微服务框架,但是我们只用到到了协议的实现,会导致整个依赖很重且没有必要。后续考虑基于connect-rpc去做连接管理,逐步移除掉对grpc-go的依赖。
3.内存泄漏问题的定位与解决,需要找一些用户看有没有遇到对应的问题,帮助定位
4.error分类,consumer调用provider过程中可能会出现多种异常,网络异常、序列化异常、server侧、业务异常、http错误码的映射,参考grpc、connect-rpc的error分类。
5.服务发现,了解应用发现、接口发现,确保服务发现机制正常运行,提升稳定性。
6.xDS,proxyless,java侧会先行实施,go这边可以参考共享java侧的文档、成果
本次采集时无评论。