-
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 deadlock due to large tasks #52884
Comments
maybe related to #51734 |
these are normal size task logs
|
we can see that in some "read all data", start key is larger than end key [2024/04/25 12:28:41.080 +08:00] [INFO] [reader.go:43] [arguments] [data-file-count=79] [stat-file-count=79] [start-key="dIAAAAAAAAFQX3KAAAAAACQVWw=="] [end-key="dIAAAAAAAAFQX3KAAAAAACLw+Q=="] |
Write an unit test to reproduce it, found one stat file has wrong content
|
print every "property" in stat file, found the problem.
And its data file has correct content |
seems caused by incorrect retry
|
Bug Report
Please answer these questions before submitting your issue. Thanks!
1. Minimal reproduce step (Required)
found by QA automatic test
2. What did you expect to see? (Required)
not deadlock
3. What did you see instead (Required)
in global sort, there should not be "There is no pairs in range" case. And "read all data start" shows we are going to read very large data, which is also not expected
4. What is your TiDB version? (Required)
The text was updated successfully, but these errors were encountered: