-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
ttl: rollback the scan trasnaction even if the BEGIN
failed. (#58943)
#58951
base: release-8.5
Are you sure you want to change the base?
ttl: rollback the scan trasnaction even if the BEGIN
failed. (#58943)
#58951
Conversation
Signed-off-by: Yang Keao <[email protected]>
This cherry pick PR is for a release branch and has not yet been approved by triage owners. To merge this cherry pick:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@ti-chi-bot: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-8.5 #58951 +/- ##
================================================
Coverage ? 15.5458%
================================================
Files ? 1629
Lines ? 598313
Branches ? 0
================================================
Hits ? 93013
Misses ? 492313
Partials ? 12987
Flags with carried forward coverage won't be shown. Click here to find out more.
|
This is an automated cherry-pick of #58943
What problem does this PR solve?
Issue Number: close #58900
Problem Summary:
Previously, the
RunInTxn
will only rollback the transaction after theBEGIN
runs successfully. However, if theBEGIN
is killed after setting the transaction status, it can still leave a valid transaction. We'll need to alsoROLLBACK
it.The effect is that when we are cancelling a TTL task (scaling the workers, stepping out of the TTL window, stopping the TTL function...), a session with valid transaction may pollute the session pool.
What changed and how does it work?
Move the
defer ... ROLLBACK
logic to the top of theRunInTxn
function.Check List
Tests
Release note