-
Notifications
You must be signed in to change notification settings - Fork 1.2k
[WIP]: add v8.5.5 release notes #21195
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 |
Co-authored-by: zhaoshangzi <[email protected]> Co-authored-by: Frank945946 <[email protected]>
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, for the ADD INDEX part.
|
@joechenrh: adding LGTM is restricted to approvers and reviewers in OWNERS files. DetailsIn 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. |
|
|
||
| 更多信息,请参考[用户文档](链接)。 | ||
|
|
||
| * 按时间点恢复 (Point-in-time recovery, PITR) 支持从压缩后的日志备份中恢复,以加快恢复速度 [#56522](https://github.com/pingcap/tidb/issues/56522) @[YuJuncen](https://github.com/YuJuncen) **tw@lilin90** <!--2001--> |
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.
这条的中文目前是从 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--> |
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.
这条的中文目前是从 v9.0.0 复制过来的之前的描述,麻烦请按照 https://github.com/pingcap/docs/pull/22190/files 里最新的英文进行调整 @lilin90
Co-authored-by: zhaoshangzi <[email protected]>
releases/release-8.5.5.md
Outdated
|
|
||
| * 提示索引下推到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" 。 |
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.
实际数据可能根据环境和负载不同有很大区别,这个数据目前是混合负载的结果,不光包含 pushdown
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.
@zhaoshangzi PTAL
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.
通过hint INDEX_LOOKUP_PUSHDOWN(t1_name, idx1_name [, idx2_name ...]) 提示优化器将指定索引查询下推到TiKV,减少远程调用的次数,性能在理论上有提升,但具体提升比例需要结合业务场景实际测试。本特性一般建议结合表 affinity 属性使用,即表属性 AFFINITY="table" 或者 分区表属性 AFFINITY="partition" 。
Co-authored-by: Frank945946 <[email protected]> Co-authored-by: JaySon <[email protected]> Co-authored-by: hongyunyan <[email protected]>
Co-authored-by: Ryan Leung <[email protected]>
Co-authored-by: Liqi Geng <[email protected]>
Signed-off-by: Weizhen Wang <[email protected]>
|
@qiancai: 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. |
| * Improved store scheduling in presence of network jitter [#9359](https://github.com/tikv/pd/issues/9359) @[okJiang](https://github.com/okJiang) **tw@qiancai** <!--2260--> | ||
|
|
||
| Provides a network status feedback mechanism to PD to avoid re-scheduling the leaders back to a problematic node (experiencing network jitter) after the leaders had been transferred off the node by TiKV raft mechanism. If the network continues to jitter, PD will actively evict leader from jittering node. |
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.
| * Improved store scheduling in presence of network jitter [#9359](https://github.com/tikv/pd/issues/9359) @[okJiang](https://github.com/okJiang) **tw@qiancai** <!--2260--> | |
| Provides a network status feedback mechanism to PD to avoid re-scheduling the leaders back to a problematic node (experiencing network jitter) after the leaders had been transferred off the node by TiKV raft mechanism. If the network continues to jitter, PD will actively evict leader from jittering node. | |
| * 提升 TiKV 在网络抖动时的调度稳定性 [#9359](https://github.com/tikv/pd/issues/9359) @[okJiang](https://github.com/okJiang) **tw@qiancai** <!--2260--> | |
| 从 v8.5.5 起,TiKV 引入网络慢节点检测与反馈机制。启用该机制后,TiKV 会在节点之间探测网络延时,计算网络慢节点分数,并将该分数上报给 PD。PD 基于该分数判断 TiKV 节点的网络状态并进行相应的调度调整:当检测到某个 TiKV 节点存在网络抖动时,PD 会限制向该节点调度新的 Leader;如果网络抖动持续存在,PD 会主动将该节点上的现有 Leader 驱逐到其他 TiKV 节点,从而降低网络异常对集群的影响。 | |
| 更多信息,请参阅[用户文档](/pd-control.md#scheduler-config-evict-slow-store-scheduler)。 |
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.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?