ddl: reuse chunk for copr-read and check context done#39473
ddl: reuse chunk for copr-read and check context done#39473ti-chi-bot merged 23 commits intopingcap:masterfrom
Conversation
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
hawkingrei
left a comment
There was a problem hiding this comment.
it work. But we maybe have a better method to solve. We have possiblity to use pool to resue object. It can be removed from binding and set Finalizer to put into pool after use. We can try it after releasing v6.5.
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 8bda001 |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 360f4ad |
|
/run-check_dev_2 |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 9a4d264 |
|
@tangenta: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
What problem does this PR solve?
Issue Number: close #39468, close #39470
Problem Summary:
For #39468, when
ADMIN CANCEL DDL JOBSis executed, the context is cancelled. However, the cop-request senders does not aware of this and keep sending to the results channel. As a result,WaitGroup.Wait()blocks forever because the cop-request senders never exit.For #39470, I found that the chunk introduced in #39382 is never reused and the runtime GC worker cannot collect it because
sync.Poolkeeps the reference. This PR uses a different way to fix #39308: it clones everything for each datum to prevent sharing the same memory.What is changed and how it works?
See the problem summary.
Check List
Tests
Before this PR:
After this PR:
Before this PR:
After this PR:
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.