Document LB connection draining behavior in NGINXaaS GCP #1617
+4
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
documentation
✅ Deploy Preview will be available once build job completes!
|
|
|
||
| ## Connection draining | ||
|
|
||
| During scale down operations, when the NGINX capacity decreases, existing connections to NGINX are given around 60s to complete before they are terminated to satisfy the scaled down capacity and no new connections to the scaled down NGINX instances are made. |
Member
There was a problem hiding this comment.
couple points I want to try and improve:
- not all connections will be subject to this, only the ones on the draining dataplane VM, but we don't talk about
BrunoVMs/instances. - "no new connections are made" -- all my traffic is dropped?!
Something a bit more like:
During scale-in operations some connections older than 60s may be Reset. The service will handle any immediate reconnects, no delay is necessary before reconnecting.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Checklist
Before sharing this pull request, I completed the following checklist:
Footnotes
Potentially sensitive information includes personally identify information (PII), authentication credentials, and live URLs. Refer to the style guide for guidance about placeholder content. ↩