You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[FEATURE] Add cleanup and update policy for application-level metadata / 为应用级 metadata 增加清理和更新策略 #3355
After #2534, metadata center usage in dubbo-go is centered on application-level metadata and service-app mapping. This issue does not propose restoring service-level provider/consumer metadata. It focuses on how application-level metadata should be updated and cleaned up in metadata centers.
changed the title [-][metadata] 为应用级 metadata 增加清理和更新策略[/-][+][FEATURE] Add cleanup and update policy for application-level metadata / 为应用级 metadata 增加清理和更新策略[/+]on May 30, 2026
Activity
[-][metadata] 为应用级 metadata 增加清理和更新策略[/-][+][FEATURE] Add cleanup and update policy for application-level metadata / 为应用级 metadata 增加清理和更新策略[/+]eye-gu commentedon Jun 4, 2026
我想到一个方案不知道可不可行: remote模式下应用元数据每天定时上报(添加心跳),上报完成后检测其他revision是不是超过N天,超过的再判断一下是不是当前存活节点中已没有该revision,如果没有,进行删除. 风险:会删除N天没有成功上报,并且在检测过程中恰好启动并上报的revision,几率很小. 如果方案可行,可以指给我
Alanxtl commentedon Jun 4, 2026
没啥问题 就是现在各 metadata center 行为不一致。Nacos 和 etcd 基本是覆盖写。Zookeeper 遇到节点已存在时直接返回 nil,不更新内容,也不刷新时间
关于几率很小的这个问题,要不加一个二次校验 先把 revision 标记为 delete-candidate,下一轮定时任务的时候再删
另外provider unregister 后 service-app mapping 是否要更新这个事情还要考虑一下。当前 provider 注册是只追加 mapping
eye-gu commentedon Jun 4, 2026
@Alanxtl
Alanxtl commentedon Jun 4, 2026
cool!
Alanxtl commentedon Jun 26, 2026
close via #3371