-
Notifications
You must be signed in to change notification settings - Fork 6.1k
ddl: move auto id handling from submitter to executor (#62449) #64761
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
base: release-8.5
Are you sure you want to change the base?
ddl: move auto id handling from submitter to executor (#62449) #64761
Conversation
|
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 |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## release-8.5 #64761 +/- ##
================================================
Coverage ? 77.1522%
================================================
Files ? 1654
Lines ? 456066
Branches ? 0
================================================
Hits ? 351865
Misses ? 82692
Partials ? 21509
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@ti-chi-bot: The following test 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. |
This is an automated cherry-pick of #62449
What problem does this PR solve?
Issue Number: close #60804
Problem Summary:
Previously, the procedure of (batch) creating table is as follow:
But if the submitter quit before waiting job finished, the post process will be skipped. So the creation itself is not atomic.
What changed and how does it work?
Now ddl owner takes the responsibility to update auto id and submitter only needs to pre-scatter the table.
tidb/pkg/ddl/job_submitter.go
Lines 224 to 227 in 1f24032
Because merged ddl job only holds the session variables from the first job for now, which means all jobs share the same variables, we don't apply pre-scatter in ddl owner.
Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.