redo(cdc): custom redo event cache and disable it by default (#10139) #10316
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an automated cherry-pick of #10139
What problem does this PR solve?
Issue Number: close #10143
What is changed and how it works?
Why disable redo event cache by default?
Redo event cache is expected to reduce CPU and I/O usage for TiCDC. However, under a heavy workload cache hit ratio is usually
0
, which means the cache doesn't make any help.In future, maybe we can generate sink/redo tasks based on
changefeed
s instead oftable
s. Then we can enable redo cache again.Check List
Tests
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note