v8.5.3: add release notes (#21399) #21606
Conversation
Co-authored-by: JaySon <[email protected]>
Co-authored-by: Bisheng Huang <[email protected]>
Co-authored-by: lidezhu <[email protected]>
Co-authored-by: xixirangrang <[email protected]>
Co-authored-by: Aolin <[email protected]>
Co-authored-by: Grace Cai <[email protected]>
Moved and revised TiCDC bug fix notes under the correct section, providing clearer descriptions for each fix. This improves the accuracy and readability of the release documentation.
Corrected 'them issue' to 'the issue' in the TiCDC section of the release-8.5.3.md notes for improved clarity.
Co-authored-by: xixirangrang <[email protected]>
Co-authored-by: Lilian Lee <[email protected]>
ti-chi-bot
added
lgtm
size/L
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Summary of Changes
Hello @ti-chi-bot, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces the official release notes for TiDB version 8.5.3. It primarily involves adding a comprehensive Markdown document detailing all compatibility changes, performance improvements, and bug fixes implemented in this version across various TiDB components like TiDB, TiKV, PD, TiFlash, and associated tools. Additionally, the pull request updates the documentation's navigation and release timeline to incorporate the new 8.5.3 entry, ensuring that users can easily access and understand the latest changes.
Highlights
- New Release Notes Document: A new Markdown file,
releases/release-8.5.3.md, has been added to document the release notes for TiDB version 8.5.3. This file details compatibility changes, various improvements, and bug fixes across different components of the TiDB ecosystem. - Table of Contents Update: The Table of Contents (
TOC.md) has been updated to include a direct link to the newly added 8.5.3 release notes, ensuring easy navigation for users looking for information on this specific version. - Release Information Updates: The main release notes page (
releases/release-notes.md) and the release timeline (releases/release-timeline.md) have both been updated to reflect the new 8.5.3 release, including its release date of August 14, 2025.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| Feature | Command | Description |
|---|---|---|
| Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
| Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
| Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
| Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Oreoxmt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Code Review
This pull request adds the release notes for TiDB v8.5.3. The changes look good overall. I've provided some suggestions to improve clarity, conciseness, and consistency, mainly in the new release-8.5.3.md file. The suggestions focus on rephrasing some descriptions for better readability and using more active voice for the bug fix entries, in line with the documentation style guide.
| - Add monitoring metrics for the merge sort stage when using Global Sort with indexes [#61025](https://github.com/pingcap/tidb/issues/61025) @[fzzf678](https://github.com/fzzf678) | ||
| - Remove redundant log entries when the `IndexLookup` operator encounters a `context canceled` error [#61072](https://github.com/pingcap/tidb/issues/61072) @[yibin87](https://github.com/yibin87) | ||
| - Improve the performance when `tidb_replica_read` is set to `closest-adaptive` [#61745](https://github.com/pingcap/tidb/issues/61745) @[you06](https://github.com/you06) | ||
| - Reduce operational costs by decreasing the amount of monitoring metrics data in large-scale clusters [#59990](https://github.com/pingcap/tidb/issues/59990) @[zimulala](https://github.com/zimulala) |
There was a problem hiding this comment.
For conciseness, consider rephrasing this item.1
| - Reduce operational costs by decreasing the amount of monitoring metrics data in large-scale clusters [#59990](https://github.com/pingcap/tidb/issues/59990) @[zimulala](https://github.com/zimulala) | |
| - Reduce operational costs by reducing monitoring metrics data in large-scale clusters [#59990](https://github.com/pingcap/tidb/issues/59990) @[zimulala](https://github.com/zimulala) |
Style Guide References
Footnotes
-
Avoid unnecessary words and repetition. ↩
| - Reduce performance jitter caused by the flow controller [#18625](https://github.com/tikv/tikv/issues/18625) @[hhwyt](https://github.com/hhwyt) | ||
| - Optimize tail latency during `ADD INDEX` operations in TiDB [#18081](https://github.com/tikv/tikv/issues/18081) @[overvenus](https://github.com/overvenus) | ||
| - Optimize the handling of `CompactedEvent` in Raftstore by moving it to the `split-check` worker, reducing blocking on the main Raftstore thread [#18532](https://github.com/tikv/tikv/issues/18532) @[LykxSassinator](https://github.com/LykxSassinator) | ||
| - Log only `SST ingest is experiencing slowdowns` when SST ingest is too slow, and skip calling `get_sst_key_ranges` to avoid performance jitter [#18549](https://github.com/tikv/tikv/issues/18549) @[LykxSassinator](https://github.com/LykxSassinator) |
There was a problem hiding this comment.
This sentence is a bit long and could be clearer. Consider rephrasing for better readability.1
| - Log only `SST ingest is experiencing slowdowns` when SST ingest is too slow, and skip calling `get_sst_key_ranges` to avoid performance jitter [#18549](https://github.com/tikv/tikv/issues/18549) @[LykxSassinator](https://github.com/LykxSassinator) | |
| - Avoid performance jitter from slow SST ingest by only logging `SST ingest is experiencing slowdowns` and skipping `get_sst_key_ranges` calls [#18549](https://github.com/tikv/tikv/issues/18549) @[LykxSassinator](https://github.com/LykxSassinator) |
Style Guide References
Footnotes
-
Make sure the documentation is easy to understand for TiDB users. ↩
|
|
||
| + PD | ||
|
|
||
| - Add GO runtime-related monitoring metrics in Prometheus [#8931](https://github.com/tikv/pd/issues/8931) @[bufferflies](https://github.com/bufferflies) |
There was a problem hiding this comment.
The language name 'Go' is usually capitalized as 'Go', not 'GO'.1
| - Add GO runtime-related monitoring metrics in Prometheus [#8931](https://github.com/tikv/pd/issues/8931) @[bufferflies](https://github.com/bufferflies) | |
| - Add Go runtime-related monitoring metrics in Prometheus [#8931](https://github.com/tikv/pd/issues/8931) @[bufferflies](https://github.com/bufferflies) |
Style Guide References
Footnotes
-
Correct English grammar, spelling, and punctuation mistakes, if any. ↩
| + Backup & Restore (BR) | ||
|
|
||
| - Improve the index restore speed during PITR by repairing indexes concurrently [#59158](https://github.com/pingcap/tidb/issues/59158) @[Leavrth](https://github.com/Leavrth) | ||
| - The Download API of TiKV supports filtering out data within a certain time range when downloading backup files, which avoids importing outdated or future data versions during restore [#18399](https://github.com/tikv/tikv/issues/18399) @[3pointer](https://github.com/3pointer) |
There was a problem hiding this comment.
This sentence is a bit long. Rephrasing it as a phrase would improve clarity and consistency with other list items.1
| - The Download API of TiKV supports filtering out data within a certain time range when downloading backup files, which avoids importing outdated or future data versions during restore [#18399](https://github.com/tikv/tikv/issues/18399) @[3pointer](https://github.com/3pointer) | |
| - Support filtering data within a specific time range in the TiKV Download API to avoid importing outdated or future data versions during restore [#18399](https://github.com/tikv/tikv/issues/18399) @[3pointer](https://github.com/3pointer) |
Style Guide References
Footnotes
-
Avoid unnecessary words and repetition. ↩
|
|
||
| + TiDB | ||
|
|
||
| - Fix the issue of incorrect key range in `ALTER RANGE meta SET PLACEMENT POLICY` [#60888](https://github.com/pingcap/tidb/issues/60888) @[nolouch](https://github.com/nolouch) |
There was a problem hiding this comment.
For conciseness and to use the preferred present tense, consider rephrasing to be more direct.1
| - Fix the issue of incorrect key range in `ALTER RANGE meta SET PLACEMENT POLICY` [#60888](https://github.com/pingcap/tidb/issues/60888) @[nolouch](https://github.com/nolouch) | |
| - Fixes an incorrect key range in `ALTER RANGE meta SET PLACEMENT POLICY` [#60888](https://github.com/pingcap/tidb/issues/60888) @[nolouch](https://github.com/nolouch) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
|
|
||
| + TiCDC | ||
|
|
||
| - Fix the issue that evaluating event filter expressions on tables containing virtual columns might cause a panic [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) |
There was a problem hiding this comment.
For clarity and conciseness, consider rephrasing to use a more active voice and the preferred present tense.1
| - Fix the issue that evaluating event filter expressions on tables containing virtual columns might cause a panic [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) | |
| - Fixes a panic that could occur when evaluating event filter expressions on tables containing virtual columns [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
| + TiCDC | ||
|
|
||
| - Fix the issue that evaluating event filter expressions on tables containing virtual columns might cause a panic [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) | ||
| - Fix the issue that the resolved ts lag keeps increasing after scaling in or out TiKV nodes on the same IP address because of outdated store IDs [#12162](https://github.com/pingcap/tiflow/issues/12162) @[3AceShowHand](https://github.com/3AceShowHand) |
There was a problem hiding this comment.
For clarity and conciseness, consider rephrasing to use a more active voice and the preferred present tense.1
| - Fix the issue that the resolved ts lag keeps increasing after scaling in or out TiKV nodes on the same IP address because of outdated store IDs [#12162](https://github.com/pingcap/tiflow/issues/12162) @[3AceShowHand](https://github.com/3AceShowHand) | |
| - Fixes an issue where the resolved ts lag kept increasing after scaling TiKV nodes in or out on the same IP address because of outdated store IDs [#12162](https://github.com/pingcap/tiflow/issues/12162) @[3AceShowHand](https://github.com/3AceShowHand) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
|
|
||
| - Fix the issue that evaluating event filter expressions on tables containing virtual columns might cause a panic [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) | ||
| - Fix the issue that the resolved ts lag keeps increasing after scaling in or out TiKV nodes on the same IP address because of outdated store IDs [#12162](https://github.com/pingcap/tiflow/issues/12162) @[3AceShowHand](https://github.com/3AceShowHand) | ||
| - Fix the issue of case-sensitive matching for column and index names in the dispatcher configuration [#12103](https://github.com/pingcap/tiflow/issues/12103) @[wk989898](https://github.com/wk989898) |
There was a problem hiding this comment.
For conciseness and to use the preferred present tense, consider rephrasing to be more direct.1
| - Fix the issue of case-sensitive matching for column and index names in the dispatcher configuration [#12103](https://github.com/pingcap/tiflow/issues/12103) @[wk989898](https://github.com/wk989898) | |
| - Fixes case-sensitive matching for column and index names in the dispatcher configuration [#12103](https://github.com/pingcap/tiflow/issues/12103) @[wk989898](https://github.com/wk989898) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
| - Fix the issue that evaluating event filter expressions on tables containing virtual columns might cause a panic [#12206](https://github.com/pingcap/tiflow/issues/12206) @[lidezhu](https://github.com/lidezhu) | ||
| - Fix the issue that the resolved ts lag keeps increasing after scaling in or out TiKV nodes on the same IP address because of outdated store IDs [#12162](https://github.com/pingcap/tiflow/issues/12162) @[3AceShowHand](https://github.com/3AceShowHand) | ||
| - Fix the issue of case-sensitive matching for column and index names in the dispatcher configuration [#12103](https://github.com/pingcap/tiflow/issues/12103) @[wk989898](https://github.com/wk989898) | ||
| - Fix the issue that configuring `column-selector` with the Debezium protocol might cause a panic [#12208](https://github.com/pingcap/tiflow/issues/12208) @[wk989898](https://github.com/wk989898) |
There was a problem hiding this comment.
For clarity and conciseness, consider rephrasing to use a more active voice and the preferred present tense.1
| - Fix the issue that configuring `column-selector` with the Debezium protocol might cause a panic [#12208](https://github.com/pingcap/tiflow/issues/12208) @[wk989898](https://github.com/wk989898) | |
| - Fixes a panic that could occur when configuring `column-selector` with the Debezium protocol [#12208](https://github.com/pingcap/tiflow/issues/12208) @[wk989898](https://github.com/wk989898) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
|
|
||
| + TiDB Lightning | ||
|
|
||
| - Fix the issue that TiDB Lightning returns the `context deadline exceeded` error when the RPC request to TiKV times out [#60143](https://github.com/pingcap/tidb/issues/60143) @[joechenrh](https://github.com/joechenrh) |
There was a problem hiding this comment.
For clarity and conciseness, consider rephrasing to use a more active voice and the preferred present tense.1
| - Fix the issue that TiDB Lightning returns the `context deadline exceeded` error when the RPC request to TiKV times out [#60143](https://github.com/pingcap/tidb/issues/60143) @[joechenrh](https://github.com/joechenrh) | |
| - Fixes an issue where TiDB Lightning returned a `context deadline exceeded` error when an RPC request to TiKV timed out [#60143](https://github.com/pingcap/tidb/issues/60143) @[joechenrh](https://github.com/joechenrh) |
Style Guide References
Footnotes
-
Prefer present tense and avoid unnecessary words. ↩
|
Warning Gemini encountered an error creating the review. You can try again by commenting |
This is an automated cherry-pick of #21399
First-time contributors' checklist
What is changed, added or deleted? (Required)
Add release notes for v8.5.3
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?