Skip to content

Conversation

@qiancai
Copy link
Collaborator

@qiancai qiancai commented Dec 16, 2025

What is changed, added or deleted? (Required)

As in the title, this PR adds the release note doc for v8.5.5.

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)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

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

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

@qiancai qiancai added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. translation/from-docs This PR is translated from a PR in pingcap/docs. labels Dec 16, 2025
@ti-chi-bot ti-chi-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 16, 2025
@ti-chi-bot ti-chi-bot bot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Dec 16, 2025
@qiancai qiancai self-assigned this Dec 16, 2025
@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 17, 2025

[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 qiancai. 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: zhaoshangzi <zhaoshangzi@icloud.com>
Co-authored-by: Frank945946 <108602632+Frank945946@users.noreply.github.com>
Copy link
Contributor

@joechenrh joechenrh left a comment

Choose a reason for hiding this comment

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

LGTM, for the ADD INDEX part.

@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 23, 2025

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

Details

In response to this:

LGTM

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.


更多信息,请参考[用户文档](链接)

* 按时间点恢复 (Point-in-time recovery, PITR) 支持从压缩后的日志备份中恢复,以加快恢复速度 [#56522](https://github.com/pingcap/tidb/issues/56522) @[YuJuncen](https://github.com/YuJuncen) **tw@lilin90** <!--2001-->
Copy link
Collaborator Author

@qiancai qiancai Dec 24, 2025

Choose a reason for hiding this comment

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

这条的中文目前是从 v9.0.0 复制过来的之前的描述,麻烦请按照 https://github.com/pingcap/docs/pull/22190/files 里最新的英文进行调整 @lilin90


更多信息,请参考[用户文档](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#graceful-shutdown-timeout-从-v855-版本开始引入)

* 提升进行中的日志备份与快照恢复的兼容性 [#58685](https://github.com/pingcap/tidb/issues/58685) @[BornChanger](https://github.com/BornChanger) **tw@lilin90** <!--2000-->
Copy link
Collaborator Author

@qiancai qiancai Dec 24, 2025

Choose a reason for hiding this comment

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

这条的中文目前是从 v9.0.0 复制过来的之前的描述,麻烦请按照 https://github.com/pingcap/docs/pull/22190/files 里最新的英文进行调整 @lilin90

@ti-chi-bot ti-chi-bot bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Dec 24, 2025
qiancai and others added 2 commits December 25, 2025 09:55
Co-authored-by: zhaoshangzi <zhaoshangzi@icloud.com>

* 提示索引下推到TiKV提升查询性能 [#62575](https://github.com/pingcap/tidb/issues/62575) @[lcwangchao](https://github.com/lcwangchao) **tw@qiancai** <!--1899-->

通过hint INDEX_LOOKUP_PUSHDOWN(t1_name, idx1_name [, idx2_name ...]) 提示优化器将指定索引查询下推到TiKV,减少远程调用的次数,经过测试数据对比显示性能可提升约20%左右,最优可提升到40%。本特性一般建议结合表 affinity 属性使用,即表属性 AFFINITY="table" 或者 分区表属性 AFFINITY="partition" 。
Copy link
Contributor

Choose a reason for hiding this comment

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

实际数据可能根据环境和负载不同有很大区别,这个数据目前是混合负载的结果,不光包含 pushdown

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Choose a reason for hiding this comment

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

通过hint INDEX_LOOKUP_PUSHDOWN(t1_name, idx1_name [, idx2_name ...]) 提示优化器将指定索引查询下推到TiKV,减少远程调用的次数,性能在理论上有提升,但具体提升比例需要结合业务场景实际测试。本特性一般建议结合表 affinity 属性使用,即表属性 AFFINITY="table" 或者 分区表属性 AFFINITY="partition" 。


* 表级和分区级亲和性属性 AFFINITY [#9764](https://github.com/tikv/pd/issues/9764) @[lhy1024](https://github.com/lhy1024) **tw@qiancai** <!--2317-->

为表或者分区表新增亲和性属性,设置亲和性属性后,PD会将表或分区的Region归为相同的一个亲和性分组中,这些Region的Leader、Voter 会被优先调度到指定TiKV Store上。有AFFNITY属性的表和分区在查询时,由于索引、表数据的Region都在一个TiKV Store上,因此优化器可结合 hint INDEX_LOOKUP_PUSHDOWN 指定将对应索引查询下推,减少跨节点分散查询带来的延迟,根据测试数据对比性能可约提升20%。
Copy link
Contributor

Choose a reason for hiding this comment

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

这个数据可能会有偏差,根据负载不同

Choose a reason for hiding this comment

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

为表或者分区表新增亲和性属性,设置亲和性属性后,PD会将表或分区的Region归为相同的一个亲和性分组中,这些Region的Leader、Voter 会被优先调度到指定TiKV Store上。有AFFNITY属性的表和分区在查询时,由于索引、表数据的Region都在一个TiKV Store上,因此优化器可结合 hint INDEX_LOOKUP_PUSHDOWN 指定将对应索引查询下推,减少跨节点分散查询带来的延迟,提升性能


* 提示索引下推到TiKV提升查询性能 [#62575](https://github.com/pingcap/tidb/issues/62575) @[lcwangchao](https://github.com/lcwangchao) **tw@qiancai** <!--1899-->

通过hint INDEX_LOOKUP_PUSHDOWN(t1_name, idx1_name [, idx2_name ...]) 提示优化器将指定索引查询下推到TiKV,减少远程调用的次数,经过测试数据对比显示性能可提升约20%左右,最优可提升到40%。本特性一般建议结合表 affinity 属性使用,即表属性 AFFINITY="table" 或者 分区表属性 AFFINITY="partition" 。

Choose a reason for hiding this comment

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

通过hint INDEX_LOOKUP_PUSHDOWN(t1_name, idx1_name [, idx2_name ...]) 提示优化器将指定索引查询下推到TiKV,减少远程调用的次数,性能在理论上有提升,但具体提升比例需要结合业务场景实际测试。本特性一般建议结合表 affinity 属性使用,即表属性 AFFINITY="table" 或者 分区表属性 AFFINITY="partition" 。


* 表级和分区级亲和性属性 AFFINITY [#9764](https://github.com/tikv/pd/issues/9764) @[lhy1024](https://github.com/lhy1024) **tw@qiancai** <!--2317-->

为表或者分区表新增亲和性属性,设置亲和性属性后,PD会将表或分区的Region归为相同的一个亲和性分组中,这些Region的Leader、Voter 会被优先调度到指定TiKV Store上。有AFFNITY属性的表和分区在查询时,由于索引、表数据的Region都在一个TiKV Store上,因此优化器可结合 hint INDEX_LOOKUP_PUSHDOWN 指定将对应索引查询下推,减少跨节点分散查询带来的延迟,根据测试数据对比性能可约提升20%。

Choose a reason for hiding this comment

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

为表或者分区表新增亲和性属性,设置亲和性属性后,PD会将表或分区的Region归为相同的一个亲和性分组中,这些Region的Leader、Voter 会被优先调度到指定TiKV Store上。有AFFNITY属性的表和分区在查询时,由于索引、表数据的Region都在一个TiKV Store上,因此优化器可结合 hint INDEX_LOOKUP_PUSHDOWN 指定将对应索引查询下推,减少跨节点分散查询带来的延迟,提升性能

@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 25, 2025

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

@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 25, 2025

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


+ TiFlash

- note [#issue](https://github.com/pingcap/tiflash/issues/${issue-id}) @[贡献者 GitHub ID](https://github.com/${github-id})
Copy link
Contributor

@JaySon-Huang JaySon-Huang Dec 25, 2025

Choose a reason for hiding this comment

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

Suggested change
- note [#issue](https://github.com/pingcap/tiflash/issues/${issue-id}) @[贡献者 GitHub ID](https://github.com/${github-id})
- 修复在 BR restore 的过程中,TiFlash 可能 panic 的问题 [#10606](https://github.com/pingcap/tiflash/issues/10606) @[CalvinNeo](https://github.com/CalvinNeo)
- 修复在 BR restore 的过程中,TiFlash 不能充分利用超过 16 核 CPU 进行数据恢复的问题 [#10605](https://github.com/pingcap/tiflash/issues/10605) @[JaySon-Huang](https://github.com/JaySon-Huang)

@ti-chi-bot
Copy link

ti-chi-bot bot commented Dec 25, 2025

@qiancai: 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 84ed814 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

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. translation/from-docs This PR is translated from a PR in pingcap/docs.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants