docs: clarify Syncpoint changefeed configuration scope

[doc-claw-bot]

What is changed, added or deleted? (Required)

Clarify that enable-sync-point is a changefeed configuration item rather than a TiCDC server configuration item.

Update the related Syncpoint wording in these docs so readers know the setting belongs to the changefeed configuration file:

• ticdc/ticdc-upstream-downstream-check.md
• dr-secondary-cluster.md

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

• master (the latest development version)
• v9.0 (TiDB 9.0 versions)
• v8.5 (TiDB 8.5 versions)
• v8.1 (TiDB 8.1 versions)
• v7.5 (TiDB 7.5 versions)
• v7.1 (TiDB 7.1 versions)
• v6.5 (TiDB 6.5 versions)

What is the related PR or file link(s)?

• This PR is translated from: docs: clarify Syncpoint changefeed configuration scope docs-cn#21838
• Other reference link(s):

AI agent involvement

• The changes in this PR were primarily made by an AI agent on behalf of the PR author.

Do your changes match any of the following descriptions?

• Delete files
• Change aliases
• Need modification after applied to another branch
• Might cause conflicts after applied to another branch

Summary by CodeRabbit

• Documentation
  • Clarified that enable-sync-point is a TiCDC changefeed configuration item.
  • Updated the prerequisites/terminology to reference creating a changefeed with Syncpoint.
  • Added/clarified how consistent snapshot points are periodically replicated to the secondary cluster when the changefeed is configured.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 64408024-40be-4810-86b6-aee68fbfd6ec

📥 Commits

Reviewing files that changed from the base of the PR and between 3c2aa57 and d015328.

📒 Files selected for processing (1)

• ticdc/ticdc-upstream-downstream-check.md

---

📝 Walkthrough

Walkthrough

The changes clarify that Syncpoint is enabled in the TiCDC changefeed configuration and explain how consistent snapshot timestamps are propagated to the secondary cluster.

Changes

Syncpoint documentation

Layer / File(s)	Summary
Clarify Syncpoint configuration and behavior dr-secondary-cluster.md, ticdc/ticdc-upstream-downstream-check.md	Updates Syncpoint guidance to reference the enable-sync-point changefeed configuration item and documents the periodic tidb_external_ts update on the secondary cluster.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main documentation change about Syncpoint scope.
Description check	✅ Passed	The description includes the required change summary, affected versions, translation link, and AI involvement.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2026-07-28 02:12:19.796074665 +0000 UTC m=+1889325.832169741: ☑️ agreed by qiancai.

[ti-chi-bot]

@asddongmen: adding LGTM is restricted to approvers and reviewers in OWNERS files.

Details

In response to this:

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.

[qiancai]

/approve

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [qiancai]

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

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-8.5: #23364.