[WIP]: add v7.5.8 release notes - #23757
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 |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe release page adds TiDB 7.5.8 metadata, one PD improvement, and bug fixes across TiDB, TiKV, PD, TiFlash, and TiCDC. ChangesTiDB 7.5.8 release notes
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This release-notes update documents TiDB 7.5.8 improvements and fixes without changing runtime behavior. No merge-readiness risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Description checkExplanation The description explains the change, target versions, branch context, and reference file. It omits the AI agent involvement section and selects master and v8.5 instead of v7.5, which does not match the TiDB 7.5.8 release notes described by the pull request. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Team
Run ID: 0262028b-df7f-4cbc-986b-9efc3ef1b7b0
📒 Files selected for processing (1)
releases/release-7.5.8.md
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review.
Co-authored-by: lidezhu <47731263+lidezhu@users.noreply.github.com>
|
@lidezhu: 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. |
|
@windtalker: 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. |
Co-authored-by: JaySon <tshent@qq.com>
qw4990
left a comment
There was a problem hiding this comment.
LGTM for the planner part
|
@qw4990: 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. |
| + TiKV | ||
|
|
||
| - Fix the issue that TiKV might panic with `txn record found but not expected` due to a race between external SST ingestion and foreground writes [#19891](https://github.com/tikv/tikv/issues/19891) @[gengliqi](https://github.com/gengliqi) <!-- component: tikv --> <!-- pr: https://github.com/tikv/tikv/pull/19914 --> | ||
| - Fix the issue that BR leaves stale GC service safepoints after a log backup task is stopped, which might block garbage collection from progressing as expected [#19832](https://github.com/tikv/tikv/issues/19832) @[Leavrth](https://github.com/Leavrth) <!-- component: br --> <!-- pr: https://github.com/tikv/tikv/pull/19913 --> |
There was a problem hiding this comment.
| - Fix the issue that BR leaves stale GC service safepoints after a log backup task is stopped, which might block garbage collection from progressing as expected [#19832](https://github.com/tikv/tikv/issues/19832) @[Leavrth](https://github.com/Leavrth) <!-- component: br --> <!-- pr: https://github.com/tikv/tikv/pull/19913 --> | |
| - Fix the issue that BR leaves stale GC service safepoints after a log backup task is stopped, which might block GC from progressing as expected [#19832](https://github.com/tikv/tikv/issues/19832) @[Leavrth](https://github.com/Leavrth) <!-- component: br --> <!-- pr: https://github.com/tikv/tikv/pull/19913 --> |
| - Fix the issue that BR leaves stale GC service safepoints after a log backup task is stopped, which might block garbage collection from progressing as expected [#19832](https://github.com/tikv/tikv/issues/19832) @[Leavrth](https://github.com/Leavrth) <!-- component: br --> <!-- pr: https://github.com/tikv/tikv/pull/19913 --> | ||
| - Fix the issue that stale connections between TiKV and TiCDC might not be fully cleaned up after TiCDC restarts or network failures, exhausting the TiKV CDC memory quota and causing changefeeds to stall [#18169](https://github.com/tikv/tikv/issues/18169) [#19610](https://github.com/tikv/tikv/issues/19610) @[asddongmen](https://github.com/asddongmen) @[wk989898](https://github.com/wk989898) <!-- component: cdc --> <!-- pr: https://github.com/tikv/tikv/pull/18864 --> <!-- pr: https://github.com/tikv/tikv/pull/19689 --> | ||
| - Fix the issue that TiKV throughput might continue to drop during a TiKV I/O hang because PD-related work is blocked by I/O operations [#17939](https://github.com/tikv/tikv/issues/17939) @[LykxSassinator](https://github.com/LykxSassinator) <!-- component: tikv --> <!-- pr: https://github.com/tikv/tikv/pull/18969 --> | ||
| - Fix the issue that foreground writes are blocked during external SST ingestion, increasing write latency during ingestion [#19954](https://github.com/tikv/tikv/issues/19954) @[gengliqi](https://github.com/gengliqi) <!-- component: tikv --> <!-- pr: https://github.com/tikv/tikv/pull/19978 --> |
There was a problem hiding this comment.
| - Fix the issue that foreground writes are blocked during external SST ingestion, increasing write latency during ingestion [#19954](https://github.com/tikv/tikv/issues/19954) @[gengliqi](https://github.com/gengliqi) <!-- component: tikv --> <!-- pr: https://github.com/tikv/tikv/pull/19978 --> |
|
@JaySon-Huang: 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. |
|
@YuhaoZhang00: 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. |
What is changed, added or deleted? (Required)
releases/release-7.5.8.mdfor the TiDB 7.5.8 patch release notes.release-8.5because the release-notes directory is maintained there and will be cherry-picked tomaster.Which TiDB version(s) do your changes apply to? (Required)
What is the related PR or file link(s)?
doc_4afdcdb19e49_release-7.5.8-updated-by-ai.mdDo your changes match any of the following descriptions?
Summary by CodeRabbit
Documentation
Bug Fixes