You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by GitBox <gi...@apache.org> on 2021/09/25 05:06:14 UTC

[GitHub] [dubbo] CrazyHZM commented on issue #1508: feature required: dubbo should consider empty protection.

CrazyHZM commented on issue #1508:
URL: https://github.com/apache/dubbo/issues/1508#issuecomment-927012038


   > Agree with your "bad data better than to lose all data" theory.
   > 
   > My question is, if we always keep the "bad data", for example, if we don't destroy all invokers when receive an empty url list, when should we clear all invokers, shouldn't there be another signal? In some scenarios, e.g., Graceful Shutdown, Offline, we need to destroy all invokers.
   
   I think we can keep bad data, call it in the original way, destroy the caller, in the Provider there is a readonly mechanism to end the caller, or gracefully go offline to end the caller, and the life cycle of the caller should not be over Controlled by the data in the registry


-- 
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: notifications-unsubscribe@dubbo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@dubbo.apache.org
For additional commands, e-mail: notifications-help@dubbo.apache.org