-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle case where grpc backend may be deregistered from registry but is still handling traffic #912
Comments
nathanejohnson
added a commit
that referenced
this issue
Dec 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is an attempt to gracefully shut down a connection to a grpc backend that gets deregistered from a registry, such as consul. This is described as point 1 in #807 . I'm not sure how common this will be, mostly a deregister event is caused by a failing health check, but this is easy enough to implement and shouldn't break anything so worth trying
The text was updated successfully, but these errors were encountered: