Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP]: add v8.5.0 release notes #19033

Open
wants to merge 30 commits into
base: master
Choose a base branch
from

Conversation

qiancai
Copy link
Collaborator

@qiancai qiancai commented Nov 11, 2024

First-time contributors' checklist

What is changed, added or deleted? (Required)

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)
  • 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)?

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. translation/from-docs This PR is translated from a PR in pingcap/docs. v8.5 labels Nov 11, 2024
@ti-chi-bot ti-chi-bot bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 11, 2024
Copy link

ti-chi-bot bot commented Nov 11, 2024

[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, ensuring that each of them provides their approval before proceeding. For more information see the Code Review Process.

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

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

@ti-chi-bot ti-chi-bot bot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Nov 11, 2024
Copy link
Member

@YangKeao YangKeao left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link

ti-chi-bot bot commented Nov 12, 2024

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

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/test-infra repository.

releases/release-8.5.0.md Outdated Show resolved Hide resolved

### 可扩展性

* Schema 缓存内存上限功能成为正式功能(GA),减少了大规模数据场景的内存占用 [#50959](https://github.com/pingcap/tidb/issues/50959) @[tiancaiamao](https://github.com/tiancaiamao) @[wjhuang2016](https://github.com/wjhuang2016) @[gmhdbjd](https://github.com/gmhdbjd) @[tangenta](https://github.com/tangenta) tw@hfxsd <!--1976-->
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
* Schema 缓存内存上限功能成为正式功能(GA),减少了大规模数据场景的内存占用 [#50959](https://github.com/pingcap/tidb/issues/50959) @[tiancaiamao](https://github.com/tiancaiamao) @[wjhuang2016](https://github.com/wjhuang2016) @[gmhdbjd](https://github.com/gmhdbjd) @[tangenta](https://github.com/tangenta) tw@hfxsd <!--1976-->
* Schema 缓存内存上限功能成为正式功能(GA),可以在集群拥有数十万甚至百万个数据库或表的场景中减少内存的使用。 [#50959](https://github.com/pingcap/tidb/issues/50959) @[tiancaiamao](https://github.com/tiancaiamao) @[wjhuang2016](https://github.com/wjhuang2016) @[gmhdbjd](https://github.com/gmhdbjd) @[tangenta](https://github.com/tangenta) tw@hfxsd <!--1976-->

releases/release-8.5.0.md Outdated Show resolved Hide resolved
releases/release-8.5.0.md Outdated Show resolved Hide resolved
releases/release-8.5.0.md Outdated Show resolved Hide resolved
releases/release-8.5.0.md Outdated Show resolved Hide resolved
releases/release-8.5.0.md Outdated Show resolved Hide resolved
Comment on lines 63 to 64
<td>提升超大规模集群的稳定性 **tw@hfxsd 1976**</td>
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。 <a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>,<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-%E4%BB%8E-v610-%E7%89%88%E6%9C%AC%E5%BC%80%E5%A7%8B%E5%BC%95%E5%85%A5">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。 PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#%E9%80%9A%E8%BF%87-active-pd-follower-%E6%8F%90%E5%8D%87-pd-region-%E4%BF%A1%E6%81%AF%E6%9F%A5%E8%AF%A2%E6%9C%8D%E5%8A%A1%E7%9A%84%E6%89%A9%E5%B1%95%E8%83%BD%E5%8A%9B">Schema 缓存控制</a>Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices#pd-%E5%BE%AE%E6%9C%8D%E5%8A%A1">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-%E4%BB%8E-v840-%E7%89%88%E6%9C%AC%E5%BC%80%E5%A7%8B%E5%BC%95%E5%85%A5">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#%E6%94%B6%E9%9B%86%E9%83%A8%E5%88%86%E5%88%97%E7%9A%84%E7%BB%9F%E8%AE%A1%E4%BF%A1%E6%81%AF">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<td>提升超大规模集群的稳定性 **tw@hfxsd 1976**</td>
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。 <a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>,<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-%E4%BB%8E-v610-%E7%89%88%E6%9C%AC%E5%BC%80%E5%A7%8B%E5%BC%95%E5%85%A5">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。 PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#%E9%80%9A%E8%BF%87-active-pd-follower-%E6%8F%90%E5%8D%87-pd-region-%E4%BF%A1%E6%81%AF%E6%9F%A5%E8%AF%A2%E6%9C%8D%E5%8A%A1%E7%9A%84%E6%89%A9%E5%B1%95%E8%83%BD%E5%8A%9B">Schema 缓存控制</a>Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices#pd-%E5%BE%AE%E6%9C%8D%E5%8A%A1">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-%E4%BB%8E-v840-%E7%89%88%E6%9C%AC%E5%BC%80%E5%A7%8B%E5%BC%95%E5%85%A5">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#%E6%94%B6%E9%9B%86%E9%83%A8%E5%88%86%E5%88%97%E7%9A%84%E7%BB%9F%E8%AE%A1%E4%BF%A1%E6%81%AF">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>
<td>提升超大规模集群的稳定性 **tw@hfxsd 1976**</td>
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。 <a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>,<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-从-v610-版本开始引入">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。 PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#通过-active-pd-follower-提升-pd-region-信息查询服务的扩展能力">Schema 缓存控制</a>Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices#pd-微服务">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-从-v840-版本开始引入">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#收集部分列的统计信息">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>

<tr>
<td rowspan="5">稳定性与高可用</td>
<td>提升超大规模集群的稳定性 **tw@hfxsd 1976**</td>
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。 <a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-从-v610-版本开始引入">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。 PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#通过-active-pd-follower-提升-pd-region-信息查询服务的扩展能力">Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-从-v840-版本开始引入">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#收集部分列的统计信息">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。 <a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-从-v610-版本开始引入">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。 PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#通过-active-pd-follower-提升-pd-region-信息查询服务的扩展能力">Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-从-v840-版本开始引入">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#收集部分列的统计信息">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>
<td>对于使用 TiDB 运行多租户应用或者 SaaS 应用的公司,经常需要存储大量的表,TiDB 在 v8.5.0 着力增强了大规模集群的稳定性。<a href="https://docs.pingcap.com/zh/tidb/v8.5/schema-cache">Schema 缓存控制</a>以及 <a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_stats_cache_mem_quota-从-v610-版本开始引入">Stats 缓存控制</a>已经成为正式功能,减少了内存过度消耗带来的稳定性问题。PD 通过 <a href="https://docs.pingcap.com/zh/tidb/v8.5/tune-region-performance#通过-active-pd-follower-提升-pd-region-信息查询服务的扩展能力">Active Follower</a> 应对大量 Region 带来的压力,并<a href="https://docs.pingcap.com/zh/tidb/v8.5/pd-microservices">将 PD 所承担的服务逐步解耦</a>,独立部署。通过<a href="https://docs.pingcap.com/zh/tidb/v8.5/system-variables#tidb_auto_analyze_concurrency-从-v840-版本开始引入">增加并发度</a>,以及<a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#收集部分列的统计信息">减少收集对象的数量</a>,统计信息收集和加载效率得到提升,保证了大集群执行计划的稳定性。</td>

Co-authored-by: Grace Cai <qqzczy@126.com>
<tr>
<td><a href="https://docs.pingcap.com/zh/tidb/v8.5/statistics#收集部分列的统计信息">统计信息收集忽略不必要的列</a>(v8.3.0 引入)</td>
<td> 在保证优化器能够获取到必要信息的前提下,加快了统计信息收集的速度,提升统计信息的时效性,进而保证选择最优的执行计划,提升集群性能。同时也降低了系统开销,改善了资源利用率。</td>
</tr>
Copy link
Member

@overvenus overvenus Nov 21, 2024

Choose a reason for hiding this comment

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

Suggested change
</tr>
</tr>
<tr>
<td><a href="https://docs.pingcap.com/zh/tidb/v8.5/tikv-in-memory-engine">MVCC 内存引擎(v8.5.0 引入)</a></td>
<td>MVCC 内存引擎通过将最新的 MVCC 版本缓存在内存中,并通过快速的 GC 机制删除内存中历史版本,从而提升 TiDB 的读性能,降低了 TiKV 扫描请求的 CPU 消耗。在遇到因 GC 时间过长导致 MVCC 版本堆积,影响读性能的时候,你可以开启 MVCC 内存引擎加速查询,提升读性能。</td>
</tr>

releases/release-8.5.0.md Outdated Show resolved Hide resolved
releases/release-8.5.0.md Outdated Show resolved Hide resolved

从 v8.5.0 开始,这两个加密功能都成为了正式功能 (GA),进一步增强了客户端数据的安全性。

更多信息,请参考 [加密备份数据](/br/br-snapshot-manual.md#encrypt-the-backup-data) 和 [加密日志备份数据](/br/br-pitr-manual.md#encrypt-the-log-backup-data)。
Copy link
Collaborator Author

@qiancai qiancai Nov 22, 2024

Choose a reason for hiding this comment

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

Suggested change
更多信息,请参考 [加密备份数据](/br/br-snapshot-manual.md#encrypt-the-backup-data)[加密日志备份数据](/br/br-pitr-manual.md#encrypt-the-log-backup-data)
更多信息,请参考[加密备份数据](/br/br-snapshot-manual.md#encrypt-the-backup-data)[加密日志备份数据](/br/br-pitr-manual.md#encrypt-the-log-backup-data)

</thead>
<tbody>
<tr>
<td rowspan="6">可扩展性与性能</td>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<td rowspan="6">可扩展性与性能</td>
<td rowspan="7">可扩展性与性能</td>


TiKV 通过静态加密功能对存储的数据进行加密,以确保数据的安全性。静态加密的安全核心点在于密钥管理。在 v8.0.0 中,TiKV 静态加密以实验特性的形式支持了基于 Google Cloud KMS 的主密钥管理。

从 v8.5.0 起,基于 Google Cloud KMS 的静态加密成为正式功能 (GA)。要启用该功能,你需要在 Google Cloud 上创建一个密钥,然后在 TiKV 配置文件中添加 `[security.encryption.master-key]` 部分的配置。
Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Suggested change
从 v8.5.0 起,基于 Google Cloud KMS 的静态加密成为正式功能 (GA)。要启用该功能,你需要在 Google Cloud 上创建一个密钥,然后在 TiKV 配置文件中添加 `[security.encryption.master-key]` 部分的配置。
从 v8.5.0 起,基于 Google Cloud KMS 的静态加密成为正式功能 (GA)。要使用该功能,你需要在 Google Cloud 上创建一个密钥,然后在 TiKV 配置文件中添加 `[security.encryption.master-key]` 部分的配置。

+ TiFlash

- note [#Issue-number](issue-link) @[Contributor-GitHub-ID](id-link)
- (dup): release-7.1.6.md > 改进提升> TiFlash - 提升聚簇索引表在后台回收过期数据的速度 [#9529](https://github.com/pingcap/tiflash/issues/9529) @[JaySon-Huang](https://github.com/JaySon-Huang)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- (dup): release-7.1.6.md > 改进提升> TiFlash - 提升聚簇索引表在后台回收过期数据的速度 [#9529](https://github.com/pingcap/tiflash/issues/9529) @[JaySon-Huang](https://github.com/JaySon-Huang)
- (dup): release-7.1.6.md > 改进提升> TiFlash - 提升聚簇索引表在后台回收过期数据的速度 [#9529](https://github.com/pingcap/tiflash/issues/9529) @[JaySon-Huang](https://github.com/JaySon-Huang)
- 更新带有更新数据场景下 Vector Search 的查询性能 [#9599](https://github.com/pingcap/tiflash/issues/9599) @[Lloyd-Pottiger](https://github.com/Lloyd-Pottiger)
- 添加关于构建 Vector Index CPU 使用率的监控指标 [#9032](https://github.com/pingcap/tiflash/issues/9032) @[JaySon-Huang](https://github.com/JaySon-Huang)
- 优化逻辑运算符的执行速度 [#9146](https://github.com/pingcap/tiflash/issues/9146) @[windtalker](https://github.com/windtalker)

+ TiFlash

- note [#Issue-number](issue-link) @[Contributor-GitHub-ID](id-link)
- (dup): release-7.1.6.md > 错误修复> TiFlash - 修复 `SUBSTRING()` 函数不支持部分整数类型的 `pos` 和 `len` 参数导致查询报错的问题 [#9473](https://github.com/pingcap/tiflash/issues/9473) @[gengliqi](https://github.com/gengliqi)
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- (dup): release-7.1.6.md > 错误修复> TiFlash - 修复 `SUBSTRING()` 函数不支持部分整数类型的 `pos` 和 `len` 参数导致查询报错的问题 [#9473](https://github.com/pingcap/tiflash/issues/9473) @[gengliqi](https://github.com/gengliqi)
- (dup): release-7.1.6.md > 错误修复> TiFlash - 修复 `SUBSTRING()` 函数不支持部分整数类型的 `pos` 和 `len` 参数导致查询报错的问题 [#9473](https://github.com/pingcap/tiflash/issues/9473) @[gengliqi](https://github.com/gengliqi)
- 修复在存算分离架构下,Vector Search 查询性能在 TiFlash write node 扩容之后,可能出现性能下降的问题 [#9637](https://github.com/pingcap/tiflash/issues/9637) @[kolafish](https://github.com/kolafish)
- 修复当 `SUBSTRING` 函数的第二个参数为负数时,可能产生错误结果的问题 [#9604](https://github.com/pingcap/tiflash/issues/9604) @[guo-shaoge](https://github.com/guo-shaoge)

Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Signed-off-by: Aolin <aolin.zhang@pingcap.com>
Copy link

ti-chi-bot bot commented Nov 22, 2024

@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 ebc904b link true /test pull-verify

Full PR test history. Your PR dashboard.

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/test-infra 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. 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. v8.5
Projects
None yet
Development

Successfully merging this pull request may close these issues.