-
Notifications
You must be signed in to change notification settings - Fork 286
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
TiCDC support checking if data is entirely replicated to Downstream #10289
Labels
affects-6.5
affects-7.1
affects-7.5
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
Comments
This was referenced Dec 21, 2023
This was referenced Jan 2, 2024
17 tasks
flowbehappy
added
affects-7.1
affects-7.5
type/bug
The issue is confirmed as a bug.
labels
Jan 29, 2024
This was referenced Jan 29, 2024
/reopen |
@hongyunyan: Reopened this issue. In response to this:
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. |
This was referenced Feb 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
affects-6.5
affects-7.1
affects-7.5
area/ticdc
Issues or PRs related to TiCDC.
severity/moderate
type/bug
The issue is confirmed as a bug.
Is your feature request related to a problem?
TiCDC provides syncing data from upstream to downstream. When no more data comes upstream, we will also curious about whether the downstream has finished syncing all the data from upstream. Thus, we need some mechanism to check whether the data is entirely replicated to downstream.
Describe the feature you'd like
We want a mechanism to check whether the data is entirely replicated to downstream easily.
Describe alternatives you've considered
No response
Teachability, Documentation, Adoption, Migration Strategy
No response
The text was updated successfully, but these errors were encountered: