Skip to content

Clarify TiKV large-row limit in transaction restraints#21830

Merged
ti-chi-bot[bot] merged 3 commits into
pingcap:masterfrom
doc-claw-bot:docs-cn/txn-raft-entry-limit
Jul 23, 2026
Merged

Clarify TiKV large-row limit in transaction restraints#21830
ti-chi-bot[bot] merged 3 commits into
pingcap:masterfrom
doc-claw-bot:docs-cn/txn-raft-entry-limit

Conversation

@doc-claw-bot

@doc-claw-bot doc-claw-bot commented Jul 22, 2026

Copy link
Copy Markdown
Collaborator

What is changed, added or deleted? (Required)

Clarify in develop/dev-guide-transaction-restraints.md that increasing the large-row limit in TiDB is not sufficient by itself. When a single write request exceeds TiKV raftstore.raft-entry-max-size, TiKV rejects the request, so users need to adjust the TiKV limit together with the TiDB row-size limit.

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).

  • 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)?

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

  • 文档
    • 补充“大事务限制”说明:TiKV 也会限制“单次写入请求”的数据量大小。
    • 当单次写入超过默认 raftstore.raft-entry-max-size(8 MiB)时,TiKV 将拒绝处理该请求。
    • 在“大行记录”场景下,建议联动调整 TiDB tidb_txn_entry_size_limit 与 TiKV raftstore.raft-entry-max-size

@ti-chi-bot ti-chi-bot Bot added contribution This PR is from a community contributor. area/develop This PR relates to the area of TiDB App development. labels Jul 22, 2026
@doc-claw-bot doc-claw-bot added type/bugfix This PR fixes a bug. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. requires-version-specific-changes After cherry-picked, the cherry-picked PR requires further changes. labels Jul 22, 2026
@ti-chi-bot ti-chi-bot Bot added missing-translation-status This PR does not have translation status info. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Jul 22, 2026
@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown

Review Change Stack

Note

Reviews paused

It 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 reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

在“大事务限制”章节补充 TiKV 写入请求大小限制,说明 raftstore.raft-entry-max-size 默认值为 8 MiB,以及大行记录场景下需同时调整 TiDB 和 TiKV 侧限制。

Changes

事务限制文档

Layer / File(s) Summary
补充 TiKV 写入请求限制说明
develop/dev-guide-transaction-restraints.md
说明超过 raftstore.raft-entry-max-size 默认 8 MiB 的写入请求会被 TiKV 拒绝,并补充大行记录下的配置调整说明。

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

Suggested labels: needs-cherry-pick-release-7.5

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed 标题准确概括了本次对 TiKV 大行限制说明的澄清。
Description check ✅ Passed 描述包含变更内容、适用版本、相关链接和 AI 参与信息,整体符合模板要求。
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.

@qiancai qiancai removed needs-cherry-pick-release-6.5 Should cherry pick this PR to release-6.5 branch. needs-cherry-pick-release-7.1 Should cherry pick this PR to release-7.1 branch. labels Jul 23, 2026
Comment thread develop/dev-guide-transaction-restraints.md Outdated
Comment thread develop/dev-guide-transaction-restraints.md Outdated
@qiancai qiancai removed the needs-cherry-pick-release-7.5 Should cherry pick this PR to release-7.5 branch. label Jul 23, 2026

@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: 1


ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 37073a70-c96e-4fd3-b29f-3bca7a313ef4

📥 Commits

Reviewing files that changed from the base of the PR and between d29bc18 and 7838533.

📒 Files selected for processing (1)
  • develop/dev-guide-transaction-restraints.md

Comment thread develop/dev-guide-transaction-restraints.md
@qiancai

qiancai commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

/approve

@qiancai qiancai added lgtm translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed missing-translation-status This PR does not have translation status info. requires-version-specific-changes After cherry-picked, the cherry-picked PR requires further changes. labels Jul 23, 2026
@qiancai qiancai self-assigned this Jul 23, 2026
@qiancai

qiancai commented Jul 23, 2026

Copy link
Copy Markdown
Collaborator

/approve

@ti-chi-bot

ti-chi-bot Bot commented Jul 23, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described 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 the approved label Jul 23, 2026
@ti-chi-bot
ti-chi-bot Bot merged commit 2c05093 into pingcap:master Jul 23, 2026
11 checks passed
@ti-chi-bot

Copy link
Copy Markdown
Member

In response to a cherrypick label: new pull request created to branch release-8.1: #21833.

@ti-chi-bot

Copy link
Copy Markdown
Member

In response to a cherrypick label: new pull request created to branch release-8.5: #21834.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/develop This PR relates to the area of TiDB App development. contribution This PR is from a community contributor. lgtm needs-cherry-pick-release-8.1 Should cherry pick this PR to release-8.1 branch. needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. type/bugfix This PR fixes a bug.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants