ddl: don't reuse the chunk until underlying memory is not referenced#39382
ddl: don't reuse the chunk until underlying memory is not referenced#39382ti-chi-bot merged 3 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. |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 009058d |
hawkingrei
left a comment
There was a problem hiding this comment.
LGTM
FYI, We have the reuse-chunk feature by #38607. we maybe able to use it.
|
/run-all-tests |
2 similar comments
|
/run-all-tests |
|
/run-all-tests |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 1399840 |
|
@tangenta PTAL |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 2642946 |
TiDB MergeCI notify✅ Well Done! New fixed [1] after this pr merged.
|
What problem does this PR solve?
Issue Number: close #39308
Problem Summary:
The issue could be reproduced easily when the data set is large enough.
The actual data underlying
types.Datumis referenced by two different goroutines, because when we initialize the datum from the chunk, we useGetString()for varchar columns.The string is not copied here!
What is changed and how it works?
Similar to
idxBufPool, this PR adds a chunksync.Poolto manage & reuse the memory as soon as possible.Check List
Tests
It is too hard to write a suitable unit test, because it needs a large amount of data and the concurrency. I test it with sysbench, no data inconsistency is found anymore.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.