-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Global sort IMPORT INTO stuck after region size is larger than 96MB #55374
Labels
affects-8.1
affects-8.3
component/ddl
This issue is related to DDL of TiDB.
severity/critical
type/bug
The issue is confirmed as a bug.
Comments
Lily2025
changed the title
import into blocked after injection one
import into blocked after injection one of tikv network partition
Aug 13, 2024
/assign D3Hunter |
ti-chi-bot
bot
added
severity/critical
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
labels
Aug 13, 2024
duplicate with #51734 |
D3Hunter
removed
may-affects-5.4
This bug maybe affects 5.4.x versions.
may-affects-6.1
may-affects-6.5
may-affects-7.1
may-affects-7.5
may-affects-8.1
labels
Aug 13, 2024
lance6716
changed the title
import into blocked after injection one of tikv network partition
Global sort IMPORT INTO stuck after region size is larger than 96MB
Aug 13, 2024
The reason is tikv's default region size is larger than 96MB after tikv/tikv#17311, and we hardcoded some calculations which assume the region size. So IMPORT INTO generates large tasks and can't allocate the memory for it. |
9 tasks
This was referenced Aug 16, 2024
ti-chi-bot bot
pushed a commit
to tikv/pd
that referenced
this issue
Aug 16, 2024
…)" (#8541) ref pingcap/tidb#55374 Revert the changes on the configuration of region-size. These changes will be delayed until v8.4. Signed-off-by: lucasliang <nkcs_lykx@hotmail.com>
ti-chi-bot bot
added a commit
to tikv/tikv
that referenced
this issue
Aug 16, 2024
ref pingcap/tidb#55374 Revert the changes on the configuration of region-size. These changes will be delayed until v8.4 Signed-off-by: lucasliang <nkcs_lykx@hotmail.com> Co-authored-by: ti-chi-bot[bot] <108142056+ti-chi-bot[bot]@users.noreply.github.com>
13 tasks
13 tasks
13 tasks
13 tasks
Mark affects-8.1 because user may manually changed the region parameters in old versions |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-8.1
affects-8.3
component/ddl
This issue is related to DDL of TiDB.
severity/critical
type/bug
The issue is confirmed as a bug.
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
1、tidb_enable_dist_task='on' and enable global sort
2、run import into
2. What did you expect to see? (Required)
import into can success
3. What did you see instead (Required)
import into blocked
the status of import job is not finished after 2h0m0s (now: 2024-08-12 23:45:55, jobId: 60004, step: importing, status: running)
operatorLogs:
[2024-08-12 21:45:54] ###### start import into
import into user_data1 from 's3://qe-testing/brie/lightning-mhy-100G-csv/sysbench.user_data1.000001*.csv?access-key=xxxxxx&secret-access-key=xxxxxx&endpoint=http%3a%2f%2fks3-cn-beijing-internal.ksyuncs.com&force-path-style=false®ion=Beijing&provider=ks' WITH DETACHED,thread=16,skip_rows=1
[2024-08-12 21:45:54] ###### wait for import job to finish
[2024-08-12 23:45:55] ###### wait for import job to finish timeout (2h0m0s)
select id, table_schema, table_name, step, status,parameters from mysql.tidb_import_jobs where start_time >= '2024-08-12 21:45:54' and table_schema = 'importtest1' and table_name = 'user_data1'
jobId: 60004, table_schema: importtest1, table_name: user_data1, step: importing, status: running
4. What is your TiDB version? (Required)
./tidb-server -V
Release Version: v8.3.0-alpha
Edition: Community
Git Commit Hash: 6df7aba
Git Branch: heads/refs/tags/v8.3.0-alpha
UTC Build Time: 2024-08-10 11:52:15
GoVersion: go1.21.10
Race Enabled: false
Check Table Before Drop: false
Store: unistore
2024-08-12T21:45:47.369+0800
The text was updated successfully, but these errors were encountered: