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.

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

Solve sink failure interrupting replication in Old Owner #2295

Closed
2 tasks done
liuzix opened this issue Jul 15, 2021 · 1 comment · Fixed by #2605
Closed
2 tasks done

Solve sink failure interrupting replication in Old Owner #2295

liuzix opened this issue Jul 15, 2021 · 1 comment · Fixed by #2605
Assignees
Labels
area/ticdc Issues or PRs related to TiCDC. component/replica-model Replication model component. difficulty/medium Medium task. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@liuzix
Copy link
Contributor

liuzix commented Jul 15, 2021

Irresponsive downstreams will block the owner until the operation times out. For example, if the Kafka broker is down and the owner tries to send a checkpoint event, the owner would not be able to do ANYTHING until the Kafka sink has timed out (if ever). This will only happen in the old owner.

Action item

  • Back port asyncSink to the old owner
  • Make old owner's DDL execution asynchronous (in changefeed.go)
@amyangfei
Copy link
Contributor

This issue is finished

@AkiraXie AkiraXie added the area/ticdc Issues or PRs related to TiCDC. label Mar 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ticdc Issues or PRs related to TiCDC. component/replica-model Replication model component. difficulty/medium Medium task. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants