Skip to content

[WIP]: add the release notes for v8.5.8 - #23522

Open
qiancai wants to merge 2 commits into
pingcap:release-8.5from
qiancai:add-8.5.8-rn
Open

[WIP]: add the release notes for v8.5.8#23522
qiancai wants to merge 2 commits into
pingcap:release-8.5from
qiancai:add-8.5.8-rn

Conversation

@qiancai

@qiancai qiancai commented Aug 13, 2026

Copy link
Copy Markdown
Collaborator

What is changed, added or deleted? (Required)

As in the title

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)

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

  • This PR is translated from:
  • Other reference link(s):

AI agent involvement

  • The changes in this PR were primarily made by an AI agent on behalf of the PR author.

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

Summary by CodeRabbit

  • Documentation
    • Added the TiDB 8.5.8 release notes.
    • Documented improvements to memory usage, query optimization, concurrency, change data capture, batching, and event processing.
    • Documented bug fixes across TiDB, TiKV, PD, BR, TiCDC, and TiDB Lightning, including stability, security, backup, scheduling, failover, checkpoint, and import reliability improvements.

@ti-chi-bot ti-chi-bot Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 13, 2026
@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Adds the TiDB 8.5.8 release notes. The document records release metadata, improvements, and bug fixes across TiDB, TiKV, PD, BR, TiCDC, and TiDB Lightning.

Changes

TiDB 8.5.8 release documentation

Layer / File(s) Summary
Release metadata and improvements
releases/release-8.5.8.md
Adds release metadata and documents improvements for TiDB, TiKV, and TiCDC.
TiDB fixes
releases/release-8.5.8.md
Documents fixes for TiDB DDL, planning, memory, parsing, security, diagnostics, and transaction behavior.
TiKV and PD fixes
releases/release-8.5.8.md
Documents fixes for backup, ingestion, scheduling, security, resource control, endpoints, and storage behavior.
BR and TiCDC fixes
releases/release-8.5.8.md
Documents BR restore fixes and TiCDC fixes for failover, checkpoints, sinks, ordering, initialization, compatibility, and resource handling.
TiDB Lightning fixes
releases/release-8.5.8.md
Documents fixes for import consistency, cleanup, Parquet decimal decoding, and canceled jobs.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: 🔵 Low · up to ae146

The PR adds release notes only, but the current text still has a duplicate component label and an imprecise workload description. These are low-impact documentation and metadata issues with no runtime effect; the PR is mergeable with explicit owner awareness or follow-up to correct them.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description includes the required headings but does not explain the changes, select the affected v8.5 version, or provide reference links. Describe the release-note changes, select v8.5 as the affected version, and add relevant reference links.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the addition of TiDB v8.5.8 release notes and accurately reflects the main change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@ti-chi-bot

ti-chi-bot Bot commented Aug 13, 2026

Copy link
Copy Markdown

[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 assign oreoxmt for approval. 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

@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Aug 13, 2026

@zhangjinpeng87 zhangjinpeng87 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM for TiKV

@ti-chi-bot

ti-chi-bot Bot commented Aug 13, 2026

Copy link
Copy Markdown

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

Details

In response to this:

LGTM for TiKV

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.

Comment thread releases/release-8.5.8.md Outdated
Comment thread releases/release-8.5.8.md Outdated
Comment thread releases/release-8.5.8.md Outdated
Comment thread releases/release-8.5.8.md Outdated
Comment thread releases/release-8.5.8.md Outdated
Co-authored-by: lidezhu <47731263+lidezhu@users.noreply.github.com>
@ti-chi-bot

ti-chi-bot Bot commented Aug 14, 2026

Copy link
Copy Markdown

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

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 2


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 703d9da1-9d1a-4dc9-b8ec-5bcca4d976e6

📥 Commits

Reviewing files that changed from the base of the PR and between 39c0c01 and ae146f9.

📒 Files selected for processing (1)
  • releases/release-8.5.8.md

Comment thread releases/release-8.5.8.md
- Fix multiple issues in TiCDC Kafka sink verification, including unexpected topic creation or other startup-only side effects, skipped Schema Registry checks for existing topics, and incorrect `replication-factor` validation for topics that TiCDC does not create [#5618](https://github.com/pingcap/ticdc/issues/5618) [#5720](https://github.com/pingcap/ticdc/issues/5720) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5811 -->
- Fix the issue that enabling claim-check causes a TiCDC Kafka sink to create a separate storage client for each encoder, increasing resource usage [#5719](https://github.com/pingcap/ticdc/issues/5719) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5811 -->
- Fix the issue that TiCDC Kafka sink errors might be inconsistently classified or wrapped, making retry classification and troubleshooting more difficult [#5790](https://github.com/pingcap/ticdc/issues/5790) @[3AceShowHand](https://github.com/3AceShowHand) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5811 -->
- Fix the issue that TiCDC might spike memory and CPU usage when bulk-creating many idle changefeeds because the coordinator does not honor the configured scheduler concurrency limit [#4831](https://github.com/pingcap/ticdc/issues/4831) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5396 -->

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Replace the ambiguous quantity.

many does not define the workload size, and Vale flagged this wording. Use a more precise phrase.

Suggested change
- Fix the issue that TiCDC might spike memory and CPU usage when bulk-creating many idle changefeeds because the coordinator does not honor the configured scheduler concurrency limit [#4831](https://github.com/pingcap/ticdc/issues/4831) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5396 -->
- Fix the issue that TiCDC might spike memory and CPU usage when bulk-creating a large number of idle changefeeds because the coordinator does not honor the configured scheduler concurrency limit [`#4831`](https://github.com/pingcap/ticdc/issues/4831) @[wlwilliamx](https://github.com/wlwilliamx) <!-- component: cdc --> <!-- pr: https://github.com/pingcap/ticdc/pull/5396 -->

As per path instructions: Markdown issues require a GitHub committable suggestion when an exact contiguous replacement is safe.

🧰 Tools
🪛 GitHub Check: vale

[warning] 104-104:
[vale] reported by reviewdog 🐶
[PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion.

Raw Output:
{"message":"[PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion.","location":{"path":"releases/release-8.5.8.md","range":{"start":{"line":104,"column":88},"end":{"line":104,"column":92}}},"severity":"INFO","code":{"value":"PingCAP.Ambiguous"}}

Sources: Path instructions, Linters/SAST tools

Comment thread releases/release-8.5.8.md
- Fix the issue that `IMPORT INTO` might report success with inconsistent indexes after a transient conflict-deletion commit error [#69792](https://github.com/pingcap/tidb/issues/69792) @[D3Hunter](https://github.com/D3Hunter) <!-- component: lightning --> <!-- pr: https://github.com/pingcap/tidb/pull/70254 -->
- Fix the issue that `IMPORT INTO` might fail with the `lock held by current process` error after an import error or retry when local engine files are not cleaned up correctly [#65645](https://github.com/pingcap/tidb/issues/65645) @[D3Hunter](https://github.com/D3Hunter) <!-- component: lightning --> <!-- pr: https://github.com/pingcap/tidb/pull/69478 -->
- Fix the issue that `IMPORT INTO` silently writes incorrect values for repeated dictionary-encoded Parquet `DECIMAL` columns [#70365](https://github.com/pingcap/tidb/issues/70365) @[joechenrh](https://github.com/joechenrh) <!-- component: lightning --> <!-- pr: https://github.com/pingcap/tidb/pull/70461 -->
- Fix the issue that `IMPORT INTO` or related local backend ingest tasks might hang when job generation is canceled [#69240](https://github.com/pingcap/tidb/issues/69240) @[D3Hunter](https://github.com/D3Hunter) <!-- component: lightning, dxf, lightning --> <!-- pr: https://github.com/pingcap/tidb/pull/70234 -->

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Remove the duplicate component label.

The metadata lists lightning twice. Keep one entry so component metadata remains unambiguous.

Suggested change
- Fix the issue that `IMPORT INTO` or related local backend ingest tasks might hang when job generation is canceled [#69240](https://github.com/pingcap/tidb/issues/69240) @[D3Hunter](https://github.com/D3Hunter) <!-- component: lightning, dxf, lightning --> <!-- pr: https://github.com/pingcap/tidb/pull/70234 -->
- Fix the issue that `IMPORT INTO` or related local backend ingest tasks might hang when job generation is canceled [`#69240`](https://github.com/pingcap/tidb/issues/69240) @[D3Hunter](https://github.com/D3Hunter) <!-- component: lightning, dxf --> <!-- pr: https://github.com/pingcap/tidb/pull/70234 -->

As per path instructions: Markdown issues require a GitHub committable suggestion when an exact contiguous replacement is safe.

Source: Path instructions

@CLAassistant

CLAassistant commented Aug 14, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

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. missing-translation-status This PR does not have translation status info. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants