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

Owner can't detect normal exit of processor #739

Closed
amyangfei opened this issue Jul 10, 2020 · 1 comment
Closed

Owner can't detect normal exit of processor #739

amyangfei opened this issue Jul 10, 2020 · 1 comment
Assignees
@amyangfei
Labels
area/ticdc Issues or PRs related to TiCDC. difficulty/medium Medium task. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/P1 The issue has P1 priority. severity/major type/bug The issue is confirmed as a bug.
Milestone
v4.0.16

Comments

@amyangfei
Copy link
Contributor

amyangfei commented Jul 10, 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.

    1. Force cancel a processor, maybe by some bug in code
    2. The owner can't detect the exit of this processor

  2. What did you expect to see?

    The owner can detect the exited of a processor.

  3. What did you see instead?

    The owner treats exited processor as normal.

    Besides, if one of the processor is blocked for some reason, should the owner detects it and kill this processor?

  4. Versions of the cluster

    • Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

      master

    • TiCDC version (execute cdc version):

      master
@amyangfei amyangfei added type/bug The issue is confirmed as a bug. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. labels Jul 10, 2020
@amyangfei amyangfei self-assigned this Jul 14, 2020
@amyangfei amyangfei added the difficulty/medium Medium task. label Jul 29, 2020
@overvenus overvenus added the priority/P1 The issue has P1 priority. label Sep 28, 2020
@amyangfei amyangfei added this to the v4.0.9 milestone Nov 11, 2020
@amyangfei amyangfei modified the milestones: v4.0.9, v4.0.10 Nov 24, 2020
@amyangfei amyangfei modified the milestones: v4.0.10, v4.0.11, v4.0.12 Jan 27, 2021
@amyangfei amyangfei modified the milestones: v4.0.12, v4.0.13 Apr 9, 2021
@amyangfei amyangfei modified the milestones: v4.0.13, v4.0.14 May 28, 2021
@amyangfei amyangfei modified the milestones: v4.0.14, v4.0.15 Aug 2, 2021
@amyangfei amyangfei modified the milestones: v4.0.15, v4.0.16 Sep 27, 2021
@AkiraXie AkiraXie added the area/ticdc Issues or PRs related to TiCDC. label Dec 6, 2021
@amyangfei
Copy link
Contributor Author

TiCDC owner has migrated to new version, ref: https://github.com/pingcap/ticdc/pull/1927

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. difficulty/medium Medium task. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. priority/P1 The issue has P1 priority. severity/major type/bug The issue is confirmed as a bug.
Projects
None yet
Milestone
v4.0.16
Development

No branches or pull requests
4 participants
@amyangfei @overvenus @jebter @AkiraXie