[Fix][MySQL-CDC]fix recovery task failure caused by binlog deletion #8587
+389
−1
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.
Purpose of this pull request
close #8586
Does this PR introduce any user-facing change?
How was this patch tested?
I can simulate and reproduce the scenario where the problem occurred
The testing steps are as follows:
step1: Start the task to synchronize data from MySQL CDC to Redis
step2: After the task synchronization is completed, execute the MySQL command "flush binary logs;" to create a new binlog file
step3: Wait to receive the binlog heartbeat event and the next checkpoint events
step4: Pause Task
step5: Execute the MySQL command “purge binary logs before 'xxx“ to delete the previous binlog file
step6: Restore Task
Error will occur before modification
After modification, the task can be restored normally
Check list
New License Guide
release-note
.