processor: fix a bug that will cause processor Tick get stuck when downstream is Kafka (#11339) #11389
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 #11339
What problem does this PR solve?
Issue Number: close #11340
What is changed and how it works?
Check List
Tests
Deploy a cdc cluster, create two changefeeds and synchronize the same table to both Kafka and TiDB separately.
Every 20 minutes, inject CDC to network isolation:
Repeat this process six times.
Before this PR, the lag in the MySQL sink changefeed was influenced by the Kafka sink changefeed when network isolation was introduced between CDC and Kafka:
After this PR, only Kafka sink changefeed lag increasing during network isolation injection:
Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note