Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[TiCDC/pre-release] Table dispatch command response is lost when owner is changed during table dispatching #4963

Closed
liuzix opened this issue Mar 21, 2022 · 0 comments · Fixed by #4942
Closed

[TiCDC/pre-release] Table dispatch command response is lost when owner is changed during table dispatching #4963

liuzix opened this issue Mar 21, 2022 · 0 comments · Fixed by #4942
Labels
affects-5.4 affects-6.0 area/ticdc Issues or PRs related to TiCDC. bug-from-internal-test Bugs found by internal testing. component/scheduler TiCDC inner scheduler component. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@liuzix
Copy link
Contributor

liuzix commented Mar 21, 2022

  • Scenario: Injects total data loss between TiCDC nodes and the whole PD cluster one at a time, i.e. prevents only one TiCDC node from contacting any PD server at each time. The replication could become stuck.
  • Root cause: The dispatch command response could arrive at the owner before the Sync message, which has been induced by an owner change. The Owner will refuse to accept the dispatch command response before the Processor is sync'ed.
  • Likelyhood: Rare. Never reproduced without using ChaosMesh.
@liuzix liuzix added component/scheduler TiCDC inner scheduler component. severity/moderate bug-from-internal-test Bugs found by internal testing. area/ticdc Issues or PRs related to TiCDC. affects-5.4 affects-6.0 labels Mar 21, 2022
@liuzix liuzix mentioned this issue Mar 21, 2022
Merged
@liuzix liuzix added the type/bug The issue is confirmed as a bug. label Mar 21, 2022
ti-chi-bot pushed a commit that referenced this issue Mar 23, 2022
@liuzix
scheduler(ticdc): Fix lost finish operation (#4942)
171a8bf 
close #4963
This was referenced Mar 23, 2022
Merged
Merged
ti-chi-bot added a commit that referenced this issue Mar 24, 2022
@ti-chi-bot
scheduler(ticdc): Fix lost finish operation (#4942) (#5001)
1e29b06 
close #4963
liuzix added a commit to ti-chi-bot/tiflow that referenced this issue Apr 21, 2022
@liuzix
scheduler(ticdc): Fix lost finish operation (pingcap#4942)
d3d7661 
close pingcap#4963
ti-chi-bot added a commit that referenced this issue Apr 21, 2022
@ti-chi-bot
scheduler(ticdc): Fix lost finish operation (#4942) (#5000)
3515f35 
close #4963
This was referenced May 7, 2022
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
affects-5.4 affects-6.0 area/ticdc Issues or PRs related to TiCDC. bug-from-internal-test Bugs found by internal testing. component/scheduler TiCDC inner scheduler component. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

scheduler(ticdc): Fix lost finish operation liuzix/ticdc
1 participant
@liuzix