-
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: do not log slow query for pessimistic write conflict retry #15890
Conversation
Codecov Report
@@ Coverage Diff @@
## master #15890 +/- ##
===============================================
- Coverage 80.4323% 80.426% -0.0063%
===============================================
Files 505 504 -1
Lines 135131 134853 -278
===============================================
- Hits 108689 108457 -232
+ Misses 17930 17898 -32
+ Partials 8512 8498 -14 |
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
/merge |
/run-all-tests |
cherry pick to release-3.0 in PR #15932 |
cherry pick to release-4.0 in PR #15933 |
/run-cherry-picker |
/run-cherry-picker |
4 similar comments
/run-cherry-picker |
/run-cherry-picker |
/run-cherry-picker |
/run-cherry-picker |
cherry pick to release-3.1 in PR #16066 |
It seems that, not for sure, we failed to cherry-pick this commit to release-3.1. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @coocood PTAL. |
What problem does this PR solve?
Problem Summary:
Slow Query is logged for each pessimistic select for update retry statement, which is confusing.
What is changed and how it works?
What's Changed:
Do not use
recordSet
, execute directly.How it Works:
recordSet
log slow query onClose
, remove it to avoid logging slow query.Related changes
Check List
Tests
Run a conflicting workload for a while and check that the slow-log file size is smaller compares to the master.