Skip to content

Conversation

@ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #21244

What is changed, added or deleted? (Required)

ref tikv/tikv#18994

Update documentation for storage.flow-control.l0-files-threshold and storage.flow-control.soft-pending-compaction-bytes-limit to reflect the behavior change introduced in TiKV PR #18994.

  • v8.5.4 and earlier: flow-control config unconditionally overrides the corresponding RocksDB config.
  • From v8.5.5: flow-control config only overrides when it is smaller than the RocksDB config, to avoid weakening RocksDB's compaction acceleration mechanism when increasing flow-control thresholds.

Also update the corresponding RocksDB config items (level0-slowdown-writes-trigger, soft-pending-compaction-bytes-limit) with the same version-specific behavior notes.

Which TiDB version(s) do your changes apply to? (Required)

  • master (the latest development version)
  • 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)
  • v5.4 (TiDB 5.4 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

hhwyt and others added 4 commits January 13, 2026 03:42
….5.5

Update documentation for storage.flow-control.l0-files-threshold and
storage.flow-control.soft-pending-compaction-bytes-limit to reflect
the behavior change introduced in TiKV PR pingcap#18994.

- v8.5.4 and earlier: flow-control config unconditionally overrides
  the corresponding RocksDB config.
- From v8.5.5: flow-control config only overrides when it is smaller
  than the RocksDB config, to avoid weakening RocksDB's compaction
  acceleration mechanism when increasing flow-control thresholds.

Also update the corresponding RocksDB config items
(level0-slowdown-writes-trigger, soft-pending-compaction-bytes-limit)
with the same version-specific behavior notes.
Use reference-based approach to avoid duplication:
- In flow-control config items, use brief note block to reference RocksDB config items
- In RocksDB config items, keep detailed version-specific behavior with links

This makes future version logic changes easier to maintain (only 2 places instead of 4).

Signed-off-by: hhwyt <[email protected]>
@ti-chi-bot ti-chi-bot added area/engine Indicates that the Issue or PR belongs to the area of TP storage or Cloud storage. contribution This PR is from a community contributor. lgtm ok-to-test Indicates a PR is ready to be tested. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. v9.0-beta.3 This PR/issue applies to TiDB v9.0-beta.3. labels Jan 13, 2026
@ti-chi-bot
Copy link

ti-chi-bot bot commented Jan 13, 2026

[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 icemap 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

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

Labels

area/engine Indicates that the Issue or PR belongs to the area of TP storage or Cloud storage. contribution This PR is from a community contributor. lgtm ok-to-test Indicates a PR is ready to be tested. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. type/cherry-pick-for-release-8.5 This PR is cherry-picked to release-8.5 from a source PR. v9.0-beta.3 This PR/issue applies to TiDB v9.0-beta.3.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants