-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
executor, server: reduce connect/disconnect log spam #19308
Conversation
/rebuild |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@nullnotnil merge failed. |
/merge |
/run-all-tests |
@nullnotnil merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@nullnotnil merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
@nullnotnil merge failed. |
/run-all-tests |
@nullnotnil merge failed. |
/merge |
Your auto merge job has been accepted, waiting for:
|
/run-all-tests |
cherry pick to release-4.0 in PR #20321 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
From a security standpoint the information that there is a new connection could be very valuable. In a normal thread pool based usage it wouldn't be that spammy. I think we need to have log sections (tags) and the ability to configure which ones are captured. This would be under the tag "connection" which could be configured to only be shown at the debug level. |
What problem does this PR solve?
Issue Number: Part of #19053 (does not close issue)
Problem Summary:
Currently there is a lot of spam in the server error log related to client activity. This makes it hard to debug issues.
What is changed and how it works?
What's Changed:
This moves three Info log messages to be Debug messages instead:
This reduces the log spam in an oltp scenario (without a connection pool) quite considerably.
Related changes
Check List
Tests
I compiled the binary and ran
while true; do mysql -e 'select 1'; sleep 1; done;
in a loop. It looks much better.Side effects
Release note