Stud-KK commented on issue #16067:
URL: https://github.com/apache/dubbo/issues/16067#issuecomment-3847031139
I’ve checked the behavior on **Dubbo 3.3.6** as suggested.
The flow is essentially the same:
- **offlineApp / onlineApp** only perform registry unregister/register
- Metadata refresh is triggered only for **service-discovery registry URLs**
via
ServiceInstanceMetadataUtils.refreshMetadataAndInstance(...)
- This results in ServiceDiscovery.update() (**service instance revision
update**),
but there is no consumer-side invoker or ExchangeClient recreation in
this QoS flow
So even on 3.3.6, existing consumer connections may remain until some other
consumer-side mechanism reacts to registry or metadata changes.
Please let me know if this behavior is expected in 3.3.x, or if you’d like me
to propose a minimal follow-up change.
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
