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.

Sign up for GitHub

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

Jump to bottom

Prevent split kv ranges on too much index data when using multi-schema change #50657

Closed
Tracked by #50752
tangenta opened this issue Jan 23, 2024 · 0 comments · Fixed by #50658
Closed
Tracked by #50752

Prevent split kv ranges on too much index data when using multi-schema change #50657

tangenta opened this issue Jan 23, 2024 · 0 comments · Fixed by #50658
Labels
type/enhancement The issue or PR belongs to an enhancement.

Comments

@tangenta
Copy link
Contributor

Enhancement

There may be too many multiFileStat. It is easy to reach the file limit supported by global sort, especially in scenarios with multi-schema changes.

tidb/pkg/ddl/backfilling_dist_scheduler.go

Lines 356 to 357 in 9f5d216

splitter, err := getRangeSplitter(
ctx, store, cloudStorageURI, int64(totalSize), int64(len(instanceIDs)), multiFileStat, logger)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/enhancement The issue or PR belongs to an enhancement.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

ddl: split range group for each index separately for global sort import tangenta/tidb
1 participant
@tangenta