release-20.2: sql/pgwire: add ops logging for draining events #66882
+29
−18
Conversation
This file contains 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
|
This change is |
Release note (ops change): Added logs for important events during the server draining/shutdown process: (1) log when the server closes an existing connection while draining, (2) log when the server rejects a new connection while draining, and (3) log when the server cancels in-flight queries after waiting for the server.shutdown.query_wait duration to elapse while draining.
rafiss
force-pushed
the
backport20.2-66817
branch
from
921ae51
to
d7f3d51
Compare
knz
approved these changes
Jun 25, 2021
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.
Backport 1/1 commits from #66817.
/cc @cockroachdb/release
Backporting for use by CC-SRE @joshimhoff
Release note (ops change): Added logs for important events during the
server draining/shutdown process: (1) log when the server closes an
existing connection while draining, (2) log when the server rejects a
new connection while draining, and (3) log when the server cancels
in-flight queries after waiting for the server.shutdown.query_wait
duration to elapse while draining.