tikv: add flow-control config override hint#9115
Conversation
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. DetailsReviewer can indicate their review by submitting an approval review. |
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
tikv-configuration-file.md
Outdated
| ### `memtables-threshold` | ||
|
|
||
| + 当 KvDB 的 memtable 的个数达到该阈值时,流控机制开始工作。 | ||
| + 当 KvDB 的 memtable 的个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).max-write-buffer-number`。 |
There was a problem hiding this comment.
| + 当 KvDB 的 memtable 的个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).max-write-buffer-number`。 | |
| + 当 KvDB 的 memtable 的个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).max-write-buffer-number` 的配置。 |
tikv-configuration-file.md
Outdated
| ### `l0-files-threshold` | ||
|
|
||
| + 当 KvDB 的 L0 文件个数达到该阈值时,流控机制开始工作。 | ||
| + 当 KvDB 的 L0 文件个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).level0-slowdown-writes-trigger`。 |
There was a problem hiding this comment.
| + 当 KvDB 的 L0 文件个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).level0-slowdown-writes-trigger`。 | |
| + 当 KvDB 的 L0 文件个数达到该阈值时,流控机制开始工作。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).level0-slowdown-writes-trigger` 的配置。 |
tikv-configuration-file.md
Outdated
| ### `soft-pending-compaction-bytes-limit` | ||
|
|
||
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制开始拒绝部分写入请求,报错 `ServerIsBusy`。 | ||
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制开始拒绝部分写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).soft-pending-compaction-bytes-limit`。 |
There was a problem hiding this comment.
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制开始拒绝部分写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).soft-pending-compaction-bytes-limit`。 | |
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制开始拒绝部分写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).soft-pending-compaction-bytes-limit` 的配置。 |
tikv-configuration-file.md
Outdated
| ### `hard-pending-compaction-bytes-limit` | ||
|
|
||
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制拒绝所有写入请求,报错 `ServerIsBusy`。 | ||
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制拒绝所有写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).hard-pending-compaction-bytes-limit`。 |
There was a problem hiding this comment.
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制拒绝所有写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).hard-pending-compaction-bytes-limit`。 | |
| + 当 KvDB 的 pending compaction bytes 达到该阈值时,流控机制拒绝所有写入请求,报错 `ServerIsBusy`。当 `enable` 的值为 `true` 时,会覆盖 `rocksdb.(defaultcf|writecf|lockcf).hard-pending-compaction-bytes-limit` 的配置。 |
|
@Connor1996 PTAL, thanks! |
Signed-off-by: Connor1996 <zbk602423539@gmail.com>
|
/verify |
|
/merge |
|
This pull request has been accepted and is ready to merge. DetailsCommit hash: 13de5b8 |
|
In response to a cherrypick label: new pull request created: #9184. |
|
In response to a cherrypick label: new pull request created: #9185. |
|
In response to a cherrypick label: new pull request created: #9186. |
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
|
In response to a cherrypick label: new pull request created: #9187. |
Signed-off-by: Connor1996 zbk602423539@gmail.com
First-time contributors' checklist
What is changed, added or deleted? (Required)
Add flow-control config override hint
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).
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?