In a scale in scenario, where a destination is removed from config, how can I detect when active connections are drained so I can terminate the server? #2942
Unanswered
cbortos-d2l
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When scaling in a cluster, I programmatically change the YARP config and remove the destination from the cluster.
I understand that the DestinationState will still live until all connections are drained.
Knowing the cluster id and the destination id, would something like this work?
If I don't get the destination, I can assume that it has drained and the state object was released.
If I get the destination, I can then check the destination's ConcurrentRequestCount value.
Can you let me know if this would work?
Thank you
Beta Was this translation helpful? Give feedback.
All reactions