vqianxiao commented on PR #15883:
URL: https://github.com/apache/dubbo/pull/15883#issuecomment-3688511100
> So you haven’t encountered the situation where invokers are refreshed
late? From my understanding of your code, if a request is being routed, the
invoker list cannot be refreshed. As a result, the refresh process will be
blocked until routing is completed. However, if routing is ongoing continuously
(e.g., a read lock is held persistently), the write lock will take much longer
to be acquired.
you are right. I found that during the release period of a service provider,
the overall Dubbo call time increased due to lock blocking until the service
provider completed the release. So, I wonder if there is a better way to solve
this problem, but currently all I can think of is to lock it first to ensure
that the call can be made normally instead of being unable to call directly
--
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]
