Open apollodafoni opened 3 days ago
/assign @CharlesCheung96
/severity major
/area ticdc
/remove-area dm
/label affects-8.2.0
@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
.
/label affects-8.2
[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.
What did you do?
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?
Versions of the cluster
ticdc git_hash
2db092244d18c043f7f8ecc85a598680b33cc324
tidb git_hash585c631742acb338c9bd0913a89efc3efb5b884a
current status of DM cluster (execute
query-status <task-name>
in dmctl)No response