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

MQ checkpoint ts at risk of early advancement #5656

Closed
Rustin170506 opened this issue May 30, 2022 · 2 comments
Closed

MQ checkpoint ts at risk of early advancement #5656

Rustin170506 opened this issue May 30, 2022 · 2 comments
Assignees
Labels
affects-6.0 affects-6.1 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.

Comments

@Rustin170506
Copy link
Member

What did you do?

MQ checkpoint ts are at risk of advancing early, and we updated the checkpoint without waiting for the flush to complete.

What did you expect to see?

No response

What did you see instead?

Wait for the flush operation to complete before updating the checkpoint.

Versions of the cluster

master

@nongfushanquan
Copy link
Contributor

/close

@ti-chi-bot
Copy link
Member

@nongfushanquan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects-6.0 affects-6.1 area/ticdc Issues or PRs related to TiCDC. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants