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

TiDB OOM at 130k table with 8C/16G #50214

Closed
kennedy8312 opened this issue Jan 9, 2024 · 2 comments · Fixed by #50186
Closed

TiDB OOM at 130k table with 8C/16G #50214

kennedy8312 opened this issue Jan 9, 2024 · 2 comments · Fixed by #50186
Assignees
Labels
affects-7.5 component/ddl This issue is related to DDL of TiDB. severity/major type/bug This issue is a bug.

Comments

@kennedy8312
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

100-1200 tables and 0-5000 partitions per schema, multiple schemas. Scale the table count on a per-database basis.
Using 8C/16G machine.

2. What did you expect to see? (Required)

TiDB could support the scenario of multiple tables/partitions.

3. What did you see instead (Required)

TiDB was OOM at a number of 130k tables.
0f699cbb-141e-4248-b695-f792787e4a69

4. What is your TiDB version? (Required)

| Release Version: v7.6.0-idx
Edition: Community
Git Commit Hash: f06bfd3
Git Branch: heads/refs/tags/v7.6.0-idx
UTC Build Time: 2024-01-08 10:08:10
GoVersion: go1.21.5
Race Enabled: false
Check Table Before Drop: false
Store: tikv |

@kennedy8312 kennedy8312 added the type/bug This issue is a bug. label Jan 9, 2024
@kennedy8312
Copy link
Author

candidate_1m

@kennedy8312
Copy link
Author

/assign zimulala

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-7.5 component/ddl This issue is related to DDL of TiDB. severity/major type/bug This issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants