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

CDC should handler properly after cluster destroy #527

Closed
zhouqiang-cl opened this issue Apr 30, 2020 · 3 comments
Closed

CDC should handler properly after cluster destroy #527

zhouqiang-cl opened this issue Apr 30, 2020 · 3 comments
Assignees
@amyangfei
Labels
area/ticdc Issues or PRs related to TiCDC. priority/P2 The issue has P2 priority. type/bug The issue is confirmed as a bug. wontfix This issue will not be fixed.

Comments

@zhouqiang-cl
Copy link
Contributor

zhouqiang-cl commented Apr 30, 2020 •
edited
Loading

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do? If possible, provide a recipe for reproducing the error.
    When the TiDB cluster destroys. CDC should work well
  2. What did you expect to see?
    It works well
  3. What did you see instead?
    It does not handle properly
@zhouqiang-cl zhouqiang-cl added the type/bug The issue is confirmed as a bug. label Apr 30, 2020
@overvenus
Copy link
Member

Can you elaborate on what you mean "work well"?

@overvenus overvenus added the priority/P2 The issue has P2 priority. label Sep 28, 2020
@amyangfei amyangfei added the status/need-discussion Issue that needs to be discussed to confirm priority, milestone, plan and task breakdown. label Nov 10, 2020
@amyangfei amyangfei self-assigned this Nov 10, 2020
@amyangfei
Copy link
Contributor

Currently TiCDC stores metadata in PD, which is a strong dependency. The upstream disaster scenario is described in #691.
As we have chosen the ts-map plus flashback way to achieve consistent replication, we don't need TiCDC to work anymore after upstream meets disaster.

@amyangfei amyangfei added wontfix This issue will not be fixed. and removed status/need-discussion Issue that needs to be discussed to confirm priority, milestone, plan and task breakdown. labels Dec 1, 2020
@amyangfei
Copy link
Contributor

won't fix

@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
Assignees

@amyangfei amyangfei

Labels
area/ticdc Issues or PRs related to TiCDC. priority/P2 The issue has P2 priority. type/bug The issue is confirmed as a bug. wontfix This issue will not be fixed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@amyangfei @overvenus @zhouqiang-cl @AkiraXie