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

The creation time of the tidb_cdc.syncpoint_v1 table of the secondary cluster does not meet expectations #11375

Open
apollodafoni opened this issue Jul 2, 2024 · 8 comments · May be fixed by #11377
Open

The creation time of the tidb_cdc.syncpoint_v1 table of the secondary cluster does not meet expectations #11375

apollodafoni opened this issue Jul 2, 2024 · 8 comments · May be fixed by #11377
Assignees
@CharlesCheung96
Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 affects-8.2 area/ticdc Issues or PRs related to TiCDC. severity/major This is a major bug. type/bug This is a bug.
Projects
Question and Bug Reports

Comments

@apollodafoni
Copy link

What did you do?

  1. Set the syncpoint interval to 5 minutes, and complete the creation of changefeeds for three clusters at 12:32:30
  2. Primary cluster: tidb_cdc.syncpoint_v1 was created at 04:35:00
  3. Secondary cluster: created at 2024-07-02 04:45:22, and it takes 13 minutes from create changefeed to tidb_cdc.syncpoint_v1
    This delay is greater than 2 syncpoint intervals
  4. The ticdc config is as follows
    bdr-mode = true
    force-replicate = true
    enable-sync-point = true
    sync-point-interval = "5m"

What did you expect to see?

The creation time of the tidb_cdc.syncpoint_v1 table of the secondary cluster within 1~2 syncpoint intervals

What did you see instead?

  • more than 2 syncpoint intervals
  • the changefeed status is warning
  • the changefeed lag is very large

Versions of the cluster

ticdc git_hash 2db092244d18c043f7f8ecc85a598680b33cc324
tidb git_hash 585c631742acb338c9bd0913a89efc3efb5b884a

current status of DM cluster (execute query-status <task-name> in dmctl)

No response
@apollodafoni apollodafoni added area/dm Issues or PRs related to DM. type/bug This is a bug. labels Jul 2, 2024
@github-actions github-actions bot added this to Need Triage in Question and Bug Reports Jul 2, 2024
@apollodafoni
Copy link
Author

/assign @CharlesCheung96

@apollodafoni
Copy link
Author

/severity major

@apollodafoni
Copy link
Author

/area ticdc

@ti-chi-bot ti-chi-bot bot added the area/ticdc Issues or PRs related to TiCDC. label Jul 2, 2024
@apollodafoni
Copy link
Author

/remove-area dm

@ti-chi-bot ti-chi-bot bot removed the area/dm Issues or PRs related to DM. label Jul 2, 2024
@apollodafoni
Copy link
Author

/label affects-8.2.0

@ti-chi-bot ti-chi-bot
Copy link
Contributor

ti-chi-bot bot commented Jul 2, 2024

@apollodafoni: The label(s) affects-8.2.0 cannot be applied. These labels are supported: duplicate, bug-from-internal-test, bug-from-user, ok-to-test, needs-ok-to-test, affects-5.4, affects-6.1, affects-6.5, affects-7.1, affects-7.5, affects-8.1, affects-8.2, may-affects-5.4, may-affects-6.1, may-affects-6.5, may-affects-7.1, may-affects-7.5, may-affects-8.1, needs-cherry-pick-release-5.4, needs-cherry-pick-release-6.1, needs-cherry-pick-release-6.5, needs-cherry-pick-release-7.1, needs-cherry-pick-release-7.5, needs-cherry-pick-release-8.1, needs-cherry-pick-release-8.2, question, release-blocker, wontfix, MariaDB.

In response to this:

/label affects-8.2.0

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 ti-community-infra/tichi repository.

@apollodafoni
Copy link
Author

/label affects-8.2

@CharlesCheung96
Copy link
Contributor 

[2024/07/02 04:40:08.276 +00:00] [ERROR] [changefeed.go:325] ["an error occurred in Owner"] [namespace=default] [changefeed=cluster-a-cluster-b] [error="[CDC:ErrMySQLTxnError]MySQL txn error: failed to create syncpoint table;: Error 8263 (HY000): The operation is not allowed while the bdr role of this cluster is set to secondary."]

The root cause is that ticdc did not set write source when creating syncpoint table.

@CharlesCheung96 CharlesCheung96 linked a pull request Jul 2, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@CharlesCheung96 CharlesCheung96

Labels
affects-6.5 affects-7.1 affects-7.5 affects-8.1 affects-8.2 area/ticdc Issues or PRs related to TiCDC. severity/major This is a major bug. type/bug This is a bug.
Projects
Question and Bug Reports
Need Triage
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

syncpoint(ticdc): set write source before creating SyncTable CharlesCheung96/tiflow
2 participants
@apollodafoni @CharlesCheung96