server: fence capture writes with etcd and P2P leases

[asddongmen]

What problem does this PR solve?

Issue Number: ref #6045

A network-isolated capture can keep writing after the surviving coordinator schedules replacement dispatchers. This creates an old/new writer overlap and can leave a MySQL sink inconsistent even after the checkpoint advances.

What is changed and how it works?

• Add a capture-wide write gate backed by fresh etcd and coordinator-issued P2P proofs.
• Renew P2P proof through capability-negotiated node heartbeat responses, with a remote witness for a coordinator colocated with its capture.
• Fence downstream writes when either proof expires; confirmed etcd session loss still exits the capture.
• Check the gate at MySQL DML execution and expose lease/admission metrics and deterministic failpoints.
• Extend capture removal grace to 10 seconds.

Already-admitted MySQL transactions remain outside the strict guarantee: the gate cannot revoke a COMMIT already accepted by the downstream.

Check List

Tests

• Unit test
• Integration test: three-capture MySQL chaos matrix and admitted-COMMIT boundary passed in TCMS plan 8228411.
• Manual test: formal 20-run stress plan 8228428 is running.

Questions

Will it cause performance regression or break compatibility?

The DML admission check is an in-memory gate. New heartbeat traffic runs every 500 ms. Enforcement is negotiated per node, so old nodes that do not advertise the capability keep legacy behavior during rolling upgrade.

Do you need to update user documentation, design documentation or monitoring documentation?

No user documentation change. New metrics expose write-lease state; the design remains an internal review draft until finalized.

Release note

Reduce the risk of duplicate MySQL sink writes during TiCDC capture network isolation by fencing writes with etcd and P2P leases.

[ti-chi-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign tenfyzhong for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

• Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[asddongmen]

/test all

[ti-chi-bot]

@asddongmen: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-cdc-mysql-integration-light	ecad0f0	link	true	/test pull-cdc-mysql-integration-light
pull-cdc-storage-integration-light	ecad0f0	link	true	/test pull-cdc-storage-integration-light
pull-cdc-pulsar-integration-heavy	ecad0f0	link	false	/test pull-cdc-pulsar-integration-heavy

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.