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.
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
Reduce "busy buffer" logs #1641
Reduce "busy buffer" logs #1641
Changes from 1 commit
0a225ca
9dfff5d
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Potential concurrency issue with
mc.clearResult()
inmc.close()
Calling
mc.clearResult()
insidemc.close()
may introduce concurrency issues becausemc.clearResult()
is not thread-safe, andmc.close()
can be invoked from multiple goroutines. Previously, the comment inmc.cleanup()
mentions avoidingmc.clearResult()
to prevent unsafe conditions.Consider removing
mc.clearResult()
frommc.close()
or ensuring it is called in a thread-safe manner to prevent race conditions.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.
Critical: Unsafe concurrent access in
close()
The
close()
method callsmc.clearResult()
which is not thread-safe, as noted in thecleanup()
method's comment: "This function can be called from multiple goroutines. So we can not mc.clearResult() here." This could lead to race conditions.Consider this safer implementation:
func (mc *mysqlConn) close() { mc.cleanup() - mc.clearResult() }
If clearing the result is necessary, consider:
clearResult()
close()
must only be called from a single goroutineclearResult()
responsibility to the caller📝 Committable suggestion
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.
cancelled connection was not closed. it caused busy buffer.
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.
this sends COM_QUIT during reading packet. It printed "busy buffer" in log.
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.
readHandshakePacket() is called during connect. And database/sql don't check ErrBadConn from connect.