include the connection id as part of the mysql conn error logs#3880
Merged
sougou merged 1 commit intovitessio:masterfrom May 1, 2018
Merged
include the connection id as part of the mysql conn error logs#3880sougou merged 1 commit intovitessio:masterfrom
sougou merged 1 commit intovitessio:masterfrom
Conversation
When troubleshooting some production issues, we noticed the slow query killer running on a couple of connections and around the same time ran into some "broken pipe" errors on the local unix socket. While it seems likely that the query killer caused the broken pipe errors, including the connection ID in both logs would help to identify this more reliably. Signed-off-by: Michael Demmer <mdemmer@slack-corp.com>
sougou
approved these changes
May 1, 2018
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When troubleshooting some production issues, we noticed the slow
query killer running on a couple of connections and around the same
time ran into some "broken pipe" errors on the local unix socket.
While it seems likely that the query killer caused the broken pipe
errors, including the connection ID in both logs would help to
identify this more reliably.
Signed-off-by: Michael Demmer mdemmer@slack-corp.com