-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Update the Compatibility changes of release-8.5.4 #21215
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
base: master
Are you sure you want to change the base?
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@Frank945946: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
Frank945946
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
| |------|------|------| | ||
| | [`rocksdb.max-manifest-file-size`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#max-manifest-file-size) | 修改 | 默认值从 `128MiB` 修改为 `256MiB`,以避免在单个 TiKV 节点的 SST 文件数量过多时,频繁触发 Manifest 文件的 compaction,从而影响整体性能 [#18889](https://github.com/tikv/tikv/issues/18889) @[glorv](https://github.com/glorv) | | ||
| | [`grpc-raft-conn-num`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-raft-conn-num) | 修改 | 默认值从 `1` 修改为 `MAX(1, MIN(4, CPU 核数 / 8))`,当 CPU 核数 ≥ 32 时,最大默认连接数限制为 4 [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | | ||
| | [`grpc-concurrency`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-concurrency) | 修改 | 默认值从 `1` 修改为 `grpc-raft-conn-num * 3 + 2` [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | [`grpc-concurrency`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-concurrency) | 修改 | 默认值从 `1` 修改为 `grpc-raft-conn-num * 3 + 2` [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | | |
| | [`grpc-concurrency`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-concurrency) | 修改 | 为实现 gRPC 相关线程配置能根据 CPU 核数进行自适应调整,默认值从 `5` 修改为 `grpc-raft-conn-num * 3 + 2` [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | |
| | 配置参数 | 类型 | 描述 | | ||
| |------|------|------| | ||
| | [`rocksdb.max-manifest-file-size`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#max-manifest-file-size) | 修改 | 默认值从 `128MiB` 修改为 `256MiB`,以避免在单个 TiKV 节点的 SST 文件数量过多时,频繁触发 Manifest 文件的 compaction,从而影响整体性能 [#18889](https://github.com/tikv/tikv/issues/18889) @[glorv](https://github.com/glorv) | | ||
| | [`grpc-raft-conn-num`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-raft-conn-num) | 修改 | 默认值从 `1` 修改为 `MAX(1, MIN(4, CPU 核数 / 8))`,当 CPU 核数 ≥ 32 时,最大默认连接数限制为 4 [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | [`grpc-raft-conn-num`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-raft-conn-num) | 修改 | 默认值从 `1` 修改为 `MAX(1, MIN(4, CPU 核数 / 8))`,当 CPU 核数 ≥ 32 时,最大默认连接数限制为 4 [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | | |
| | [`grpc-raft-conn-num`](https://docs.pingcap.com/zh/tidb/v8.5/tikv-configuration-file#grpc-raft-conn-num) | 修改 | 为实现 gRPC 相关线程配置能根据 CPU 核数进行自适应调整,默认值从 `1` 修改为 `MAX(1, MIN(4, CPU 核数 / 8))`,当 CPU 核数 ≥ 32 时,最大默认连接数限制为 4 [#18806](https://github.com/tikv/tikv/issues/18806) @[LykxSassinator](https://github.com/LykxSassinator) | |
| ### 系统变量 | ||
|
|
||
| - 系统变量 [`tidb_mpp_store_fail_ttl`](https://docs.pingcap.com/zh/tidb/v8.5/system-variables/#tidb_mpp_store_fail_ttl) 默认值从 `60s` 修改为 `0s`,意味着 TiDB 不再需要额外等待即可向新启动的 TiFlash 节点发送查询请求,无需再通过延迟来避免查询失败 [#61826](https://github.com/pingcap/tidb/issues/61826) @[gengliqi](https://github.com/gengliqi) | ||
| 新建的 v8.5.3 集群可以平滑升级到 v8.5.4。但 v8.5.4 发布包含若干系统变量和配置参数的默认值变更和行为调整,需要注意以下要点: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| 新建的 v8.5.3 集群可以平滑升级到 v8.5.4。但 v8.5.4 发布包含若干系统变量和配置参数的默认值变更和行为调整,需要注意以下要点: | |
| 新建的 v8.5.3 集群可以平滑升级到 v8.5.4。但 v8.5.4 发布包含若干系统变量和配置参数的默认值变更和行为调整,升级时需要注意以下要点: |
| 新建的 v8.5.3 集群可以平滑升级到 v8.5.4。但 v8.5.4 发布包含若干系统变量和配置参数的默认值变更和行为调整,需要注意以下要点: | ||
|
|
||
| - 系统变量 [`tidb_replica_read`](https://docs.pingcap.com/zh/tidb/v8.5/system-variables/#tidb_replica_read-从-v40-版本开始引入) 从 v8.5.4 开始仅对只读 SQL 语句生效,以提高数据读取的安全性并减少与其他功能的重叠 [#62856](https://github.com/pingcap/tidb/issues/62856) @[you06](https://github.com/you06) | ||
| - 大多数变更对于常规升级是安全的,但对于曾进行过性能调优、使用 TiFlash、或对 TiKV compaction 进行了自定义配置的集群,需要仔细检查本节内容。 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| - 大多数变更对于常规升级是安全的,但对于曾进行过性能调优、使用 TiFlash、或对 TiKV compaction 进行了自定义配置的集群,需要仔细检查本节内容。 | |
| - 大多数变更对于常规升级是安全的,但对于曾进行过性能调优、包含 TiFlash 节点、或对 TiKV compaction 进行了自定义配置的集群,需要仔细检查本节内容。 |
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 (in Chinese).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?