Skip to content

ticdc: clarify rolling upgrade guidance#21496

Open
wlwilliamx wants to merge 12 commits intopingcap:masterfrom
wlwilliamx:ticdc/clarify-old-arch-upgrade-guidance
Open

ticdc: clarify rolling upgrade guidance#21496
wlwilliamx wants to merge 12 commits intopingcap:masterfrom
wlwilliamx:ticdc/clarify-old-arch-upgrade-guidance

Conversation

@wlwilliamx
Copy link
Copy Markdown
Contributor

@wlwilliamx wlwilliamx commented Apr 1, 2026

What is changed, added or deleted? (Required)

Clarify the rolling-upgrade guidance for old-architecture TiCDC.

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

  • master (the latest development version)
  • v8.5 (TiDB 8.5 versions)
  • v8.4 (TiDB 8.4 versions)
  • v8.3 (TiDB 8.3 versions)
  • v8.2 (TiDB 8.2 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)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)
  • v5.3 (TiDB 5.3 versions)

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

  • This PR is translated from:

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

@wlwilliamx wlwilliamx added the area/ticdc Indicates that the Issue or PR belongs to the area of TiCDC. label Apr 1, 2026
@ti-chi-bot ti-chi-bot bot added missing-translation-status This PR does not have translation status info. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 1, 2026
@ti-chi-bot ti-chi-bot bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. and removed size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 1, 2026
@wlwilliamx wlwilliamx changed the title ticdc: clarify old-architecture rolling upgrade guidance ticdc: clarify rolling upgrade guidance Apr 1, 2026

## 历史版本升级的兼容性说明

TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化。因此,TiCDC 不对与更高版本 TiDB/TiKV/PD 的跨版本混部提供正式的向上兼容性保证。
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

分别描述向下、向上兼容情况。并分别举个例子

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

向下兼容需要说支持 v6.5+ 吗

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

不兼容啊 Orz。老架构全都不支持跨版本兼容。只有新架构 8.5.4 开始才支持从 7.5 开始兼容

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@wlwilliamx
Copy link
Copy Markdown
Contributor Author

/retest

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 1, 2026

@flowbehappy: 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.

@lilin90 lilin90 self-assigned this Apr 2, 2026
@lilin90 lilin90 added the translation/doing This PR’s assignee is translating this PR. label Apr 2, 2026
@ti-chi-bot ti-chi-bot bot removed the missing-translation-status This PR does not have translation status info. label Apr 2, 2026
@lilin90 lilin90 added needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. labels Apr 2, 2026
@lilin90 lilin90 requested review from hfxsd and lilin90 April 2, 2026 03:01

## 历史版本升级的兼容性说明

TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能。这些功能的实现会修改相关的逻辑和数据处理流程,TiCDC 需要做相应的适配。因此,**老架构 TiCDC 不对与跨版本的 TiDB/TiKV/PD 混部提供正式的向上和向下兼容**性保证。在新架构中 TiCDC 中,我们会确保对 v7.5.0 及以上版本的 TiDB 集群的**向下兼容性**。
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能。这些功能的实现会修改相关的逻辑和数据处理流程,TiCDC 需要做相应的适配。因此,**老架构 TiCDC 不对与跨版本的 TiDB/TiKV/PD 混部提供正式的向上和向下兼容**性保证。在新架构中 TiCDC 中,我们会确保对 v7.5.0 及以上版本的 TiDB 集群的**向下兼容性**
TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能。这些功能的实现会修改相关的逻辑和数据处理流程,TiCDC 需要做相应的适配。因此,**老架构 TiCDC 不对与跨版本的 TiDB/TiKV/PD 混部提供正式的向上和向下兼容性保证**。在新架构中 TiCDC 中,我们会确保对 v7.5.0 及以上版本的 TiDB 集群的**向下兼容性**


- TiDB 目前暂不支持版本降级或升级后回退。
- 支持 TiCDC,TiFlash 等组件版本的升级。
- 如果集群中包含基于老架构实现的 TiCDC 历史版本(例如 `v6.5.0` 到 `v8.5.5`),不建议在 TiDB 滚动升级期间持续运行 changefeed。若目标 TiDB 版本高于老架构 TiCDC,必须先升级 TiCDC,升级到时,建议按“暂停所有 changefeed -> 升级 TiCDC -> 升级 TiDB 集群 -> 恢复 changefeed”的顺序执行。更多说明请参考 [TiCDC 历史版本滚动升级兼容性说明](/ticdc/ticdc-compatibility.md#历史版本升级的兼容性说明)。
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- 如果集群中包含基于老架构实现的 TiCDC 历史版本(例如 `v6.5.0``v8.5.5`),不建议在 TiDB 滚动升级期间持续运行 changefeed。若目标 TiDB 版本高于老架构 TiCDC,必须先升级 TiCDC,升级到时,建议按“暂停所有 changefeed -> 升级 TiCDC -> 升级 TiDB 集群 -> 恢复 changefeed”的顺序执行。更多说明请参考 [TiCDC 历史版本滚动升级兼容性说明](/ticdc/ticdc-compatibility.md#历史版本升级的兼容性说明)
- 如果集群中包含基于老架构实现的 TiCDC 历史版本(例如 `v6.5.0``v8.5.5`),不建议在 TiDB 滚动升级期间持续运行 Changefeed。若目标 TiDB 版本高于老架构 TiCDC,必须先升级 TiCDC,升级到时,建议按“暂停所有 Changefeed -> 升级 TiCDC -> 升级 TiDB 集群 -> 恢复 Changefeed”的顺序执行。更多说明请参考 [TiCDC 历史版本滚动升级兼容性说明](/ticdc/ticdc-compatibility.md#历史版本升级的兼容性说明)

Co-authored-by: xixirangrang <hfxsd@hotmail.com>
Co-authored-by: lidezhu <47731263+lidezhu@users.noreply.github.com>
@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 3, 2026

[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 ask for approval from lilin90. 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:

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

Co-authored-by: lidezhu <47731263+lidezhu@users.noreply.github.com>
@ti-chi-bot ti-chi-bot bot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Apr 3, 2026

## 历史版本升级的兼容性说明

TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能。这些功能的实现会修改相关的逻辑和数据处理流程,TiCDC 需要做相应的适配。因此,**老架构 TiCDC 不对与跨版本的 TiDB/TiKV/PD 混部提供正式的向上和向下兼容性保证**。在新架构中 TiCDC 中,支持对 v7.5.0 及以上版本的 TiDB 集群的**向下兼容性**。
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关产品持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能。这些功能的实现会修改相关的逻辑和数据处理流程,TiCDC 需要做相应的适配。因此,**老架构 TiCDC 不对与跨版本的 TiDB/TiKV/PD 混部提供正式的向上和向下兼容性保证**在新架构中 TiCDC 中,支持对 v7.5.0 及以上版本的 TiDB 集群的**向下兼容性**
TiCDC 依赖 TiDB、TiKV 和 PD 提供的上游变更数据及相关接口。随着 TiDB 及相关组件的持续演进,这些数据格式和接口可能发生变化,例如 TiDB 的并行 DDL、快速建表等功能会修改相关逻辑和数据处理流程,TiCDC 需要进行相应适配。因此,**老架构 TiCDC 不保证在跨版本的 TiDB/TiKV/PD 混合部署环境中提供正式的向上和向下兼容性**新架构 TiCDC 支持对 v7.5.0 及以上版本的 TiDB 集群提供**向下兼容性**


- TiDB 目前暂不支持版本降级或升级后回退。
- 支持 TiCDC,TiFlash 等组件版本的升级。
- 如果集群中包含基于老架构实现的 TiCDC 历史版本(例如 `v6.5.0` 到 `v8.5.5`),不建议在 TiDB 滚动升级期间持续运行 Changefeed。若目标 TiDB 版本高于老架构 TiCDC,必须先升级 TiCDC。升级的时候,建议按“暂停所有 Changefeed -> 升级 TiCDC -> 升级 TiDB 集群 -> 恢复 Changefeed”的顺序执行。更多说明请参考 [TiCDC 历史版本滚动升级兼容性说明](/ticdc/ticdc-compatibility.md#历史版本升级的兼容性说明)。
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这里是指从 v6.5.0 升级到 v8.5.5,还是 v6.5.0v8.5.5 的版本都是老架构版本?读起来有点歧义。如果是第二个意思,https://docs.pingcap.com/zh/tidb/stable/release-8.5.4/ 新架构是 v8.5.4 引入的,有点矛盾。

@ti-chi-bot
Copy link
Copy Markdown

ti-chi-bot bot commented Apr 3, 2026

@wlwilliamx: The following test 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-verify 8dc0365 link true /test pull-verify

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/ticdc Indicates that the Issue or PR belongs to the area of TiCDC. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. translation/doing This PR’s assignee is translating this PR.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants