Skip to content
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

Merged
merged 3 commits into from
Mar 31, 2020

Conversation

coocood
Copy link
Member

@coocood coocood commented Mar 31, 2020

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 on Close, remove it to avoid logging slow query.

Related changes

  • Need to cherry-pick to the release branch

Check List

Tests

  • Manual test (add detailed scripts or steps below)
    Run a conflicting workload for a while and check that the slow-log file size is smaller compares to the master.

@coocood coocood added type/enhancement The issue or PR belongs to an enhancement. sig/execution SIG execution needs-cherry-pick-3.0 labels Mar 31, 2020
@coocood coocood requested a review from a team as a code owner March 31, 2020 06:38
@ghost ghost requested review from SunRunAway and removed request for a team March 31, 2020 06:38
@coocood
Copy link
Member Author

coocood commented Mar 31, 2020

@jackysp @lysu PTAL

@codecov
Copy link

codecov bot commented Mar 31, 2020

Codecov Report

Merging #15890 into master will decrease coverage by 0.0062%.
The diff coverage is 100%.

@@               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

Copy link
Member

@jackysp jackysp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jackysp jackysp added the status/LGT1 Indicates that a PR has LGTM 1. label Mar 31, 2020
Copy link
Contributor

@lysu lysu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lysu
Copy link
Contributor

lysu commented Mar 31, 2020

/merge

@sre-bot sre-bot added the status/can-merge Indicates a PR has been approved by a committer. label Mar 31, 2020
@lysu lysu added status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Mar 31, 2020
@sre-bot
Copy link
Contributor

sre-bot commented Mar 31, 2020

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Mar 31, 2020

cherry pick to release-3.0 in PR #15932

@sre-bot
Copy link
Contributor

sre-bot commented Mar 31, 2020

cherry pick to release-4.0 in PR #15933

@lysu
Copy link
Contributor

lysu commented Apr 1, 2020

/run-cherry-picker

@XuHuaiyu
Copy link
Contributor

XuHuaiyu commented Apr 3, 2020

/run-cherry-picker

4 similar comments
@XuHuaiyu
Copy link
Contributor

XuHuaiyu commented Apr 3, 2020

/run-cherry-picker

@lysu
Copy link
Contributor

lysu commented Apr 3, 2020

/run-cherry-picker

@you06
Copy link
Contributor

you06 commented Apr 3, 2020

/run-cherry-picker

@you06
Copy link
Contributor

you06 commented Apr 3, 2020

/run-cherry-picker

@sre-bot
Copy link
Contributor

sre-bot commented Apr 3, 2020

cherry pick to release-3.1 in PR #16066

@sre-bot
Copy link
Contributor

sre-bot commented Apr 7, 2020

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/execution SIG execution status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants