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

TiDB Server OOM when the table# and paration# is large #50077

Closed
kennedy8312 opened this issue Jan 4, 2024 · 2 comments · Fixed by #50062
Closed

TiDB Server OOM when the table# and paration# is large #50077

kennedy8312 opened this issue Jan 4, 2024 · 2 comments · Fixed by #50062
Assignees
@zimulala
Labels
affects-6.5 affects-7.1 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

kennedy8312 commented Jan 4, 2024 •
edited by zimulala
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

Create 400-1000 tables and >3000 partitions per schema, multiple schemas. Scale the table count to 540k on a per-database basis.

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

TiDB can handle this level of SaaS usage.

3. What did you see instead (Required)

TiDB server OOM with 8c/32g machine.
image

4. What is your TiDB version? (Required)

master
@kennedy8312 kennedy8312 added the type/bug This issue is a bug. label Jan 4, 2024
@zimulala zimulala self-assigned this Jan 4, 2024
@jebter jebter added severity/major component/ddl This issue is related to DDL of TiDB. labels Jan 4, 2024
@zimulala zimulala mentioned this issue Jan 4, 2024
Merged
13 tasks
@zimulala zimulala removed may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 sig/sql-infra SIG: SQL Infra labels Jan 4, 2024
@kennedy8312
Copy link
Author

candidate_1m

@kennedy8312
Copy link
Author

TiDB would be OOM at the level of 130k table + ~650k partitions, in a 3-node 8C/16G TiDB env.
截屏2024-01-08 10 05 30

ti-chi-bot bot pushed a commit that referenced this issue Jan 8, 2024
@zimulala
*: memory is not allocated first if the user does not use some inform…
e56efc6 
…ation from the table. (#50062)

close #50077
This was referenced Jan 8, 2024
Merged
Merged
Merged
@zimulala zimulala mentioned this issue Jan 9, 2024
Closed
3 tasks
AilinKid pushed a commit to AilinKid/tidb that referenced this issue Jan 17, 2024
@zimulala @AilinKid
*: memory is not allocated first if the user does not use some inform…
14b58e6 
…ation from the table. (pingcap#50062)

close pingcap#50077
ti-chi-bot bot pushed a commit that referenced this issue Jan 25, 2024
@ti-chi-bot
*: memory is not allocated first if the user does not use some inform…
97a9bf8 
…ation from the table. (#50062) (#50171)

close #50077
ti-chi-bot bot pushed a commit that referenced this issue Feb 1, 2024
@ti-chi-bot
*: memory is not allocated first if the user does not use some inform…
634602f 
…ation from the table. (#50062) (#50169)

close #50077
ti-chi-bot bot pushed a commit that referenced this issue Feb 22, 2024
@ti-chi-bot
*: memory is not allocated first if the user does not use some inform…
6915d3a 
…ation from the table. (#50062) (#50166)

close #50077
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimulala zimulala

Labels
affects-6.5 affects-7.1 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
Milestone
No milestone
3 participants
@zimulala @jebter @kennedy8312