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
After #2534, dubbo-go's metadata main path focuses on application-level metadata. Revision is the key signal used by consumers to determine whether remote MetadataInfo has changed. This issue only focuses on application-level metadata revision and does not cover service-level ServiceDefinition.
The current revision calculation mainly uses application, path, version, port, and method, then sums CRC32 values. This rule is relatively coarse and may not cover all metadata fields that affect service discovery behavior.
Potential problems:
Revision may not change when group, protocol, or selected URL params change.
Different URL combinations may have weak collision risks.
Revision is not strongly bound to the serialized MetadataInfo content.
Consumers may continue using stale metadata cache when revision does not change.
Suggestions
Define the input fields for application-level metadata revision.
Prefer calculating revision from a canonical representation of MetadataInfo.
Make ordering, serialization, and hash rules deterministic.
Add tests proving revision changes when group, protocol, params, or methods change.
Provide compatibility or migration strategy if the algorithm changes.
Activity
[-][metadata] 改进应用级 metadata revision 计算规则[/-][+][FEATURE] Improve application-level metadata revision calculation / 改进应用级 metadata revision 计算[/+]Qiao-yq commentedon May 30, 2026
Can I take this up?
Alanxtl commentedon Jun 25, 2026
close via #3370