TiDB v6.1.0: Modifying the rocksdb.defaultcf.soft-pending-compaction-bytes-limit parameter online via set config or tikv-ctl does not take effect

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: tidb v6.1.0 通过set config 或 tikv-ctl 在线修改rocksdb.defaultcf.soft-pending-compaction-bytes-limit参数后,没有生效

| username: 找到cc

[TiDB Usage Environment] Production Environment
[TiDB Version] V6.1.0
[Encountered Problem: Problem Phenomenon and Impact]

  1. View
    show config where type=‘tikv’ and name=‘rocksdb.defaultcf.soft-pending-compaction-bytes-limit’;
    show config where type=‘tikv’ and name=‘rocksdb.defaultcf.hard-pending-compaction-bytes-limit’;

  2. Modify:
    set config tikv rocksdb.defaultcf.soft-pending-compaction-bytes-limit= “256GB”;
    set config tikv rocksdb.defaultcf.hard-pending-compaction-bytes-limit= “2000GB”;

  3. View again: found that the default values have not been modified
    show config where type=‘tikv’ and name=‘rocksdb.defaultcf.soft-pending-compaction-bytes-limit’;
    show config where type=‘tikv’ and name=‘rocksdb.defaultcf.hard-pending-compaction-bytes-limit’;

  4. Check the configuration file of the tikv node and found that it has been modified

[rocksdb.defaultcf]
level0-file-num-compaction-trigger = 4
soft-pending-compaction-bytes-limit = “256GB”
hard-pending-compaction-bytes-limit = “2000GB”
[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

2
| username: 找到cc | Original post link

The reason has been found. When the value of storage.flow-control.enable is true, the configuration of storage.flow-control.hard-pending-compaction-bytes-limit will override the configuration of rocksdb.(defaultcf|writecf|lockcf).hard-pending-compaction-bytes-limit.

3
| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.