Skip to content

docs: fix TiKV RocksDB block-size defaults#21808

Merged
ti-chi-bot[bot] merged 2 commits into
pingcap:masterfrom
doc-claw-bot:docs/fix-tikv-block-size-default
Jul 15, 2026
Merged

docs: fix TiKV RocksDB block-size defaults#21808
ti-chi-bot[bot] merged 2 commits into
pingcap:masterfrom
doc-claw-bot:docs/fix-tikv-block-size-default

Conversation

@doc-claw-bot

Copy link
Copy Markdown
Collaborator

What is changed, added or deleted? (Required)

Fixes the outdated default RocksDB block-size value in the following TiKV Chinese docs:

  • storage-engine/rocksdb-overview.md
  • tune-tikv-memory-performance.md

These documents said the default block size is 64KB, but the TiKV config template uses 32KB for rocksdb.defaultcf and rocksdb.writecf.

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)
  • v6.1 (TiDB 6.1 versions)

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

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

@doc-claw-bot doc-claw-bot added needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. type/bugfix This PR fixes a bug. labels Jul 15, 2026
@ti-chi-bot ti-chi-bot Bot added contribution This PR is from a community contributor. 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 15, 2026
@doc-claw-bot doc-claw-bot added translation/from-docs This PR is translated from a PR in pingcap/docs. and removed missing-translation-status This PR does not have translation status info. labels Jul 15, 2026
Comment thread tune-tikv-memory-performance.md Outdated
@qiancai qiancai added the ONCALL Relates to documentation oncall. label Jul 15, 2026
@qiancai

qiancai commented Jul 15, 2026

Copy link
Copy Markdown
Collaborator

/approve

@qiancai qiancai added the lgtm label Jul 15, 2026
@ti-chi-bot

ti-chi-bot Bot commented Jul 15, 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 15, 2026
@qiancai qiancai self-assigned this Jul 15, 2026
@ti-chi-bot
ti-chi-bot Bot merged commit 5a1d9cb into pingcap:master Jul 15, 2026
9 of 10 checks passed
@ti-chi-bot

Copy link
Copy Markdown
Member

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

qiancai added a commit that referenced this pull request Jul 15, 2026
Co-authored-by: doc-claw-bot <qian.cai@outlook.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved contribution This PR is from a community contributor. lgtm needs-cherry-pick-release-8.5 Should cherry pick this PR to release-8.5 branch. ONCALL Relates to documentation oncall. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. translation/from-docs This PR is translated from a PR in pingcap/docs. type/bugfix This PR fixes a bug.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants