gian/cubefs
1
0
Fork 0
mirror of https://github.com/cubefs/cubefs.git synced 2026-08-02 02:00:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

docs(config): add punishment docs for blob delete and shard repair

Browse Source 
Signed-off-by: pengtianyue <pengtianyue@oppo.com>
This commit is contained in:
pengtianyue 2023-06-06 16:46:47 +08:00 committed by pengtianyue
parent 374cda014b
commit 75bdb5ff7b
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs-zh/source/maintenance/configs/blobstore/scheduler.md
View File

@ -192,6 +192,8 @@ v3.3.0版本开始支持并发修复磁盘。
### shard_repair示例
* task_pool_size，修补任务的并发度，默认10
* message_punish_threshold，惩罚阈值，如果对应消费失败次数超过该值，则会惩罚一段时间，避免短时间内大量重试，默认3次
* message_punish_time_m，惩罚时间，默认10分钟
* orphan_shard_log，记录修补失败的孤本信息，dir需要配置，chunkbits为日志文件轮转大小，默认29（2^29字节）
```json
{
@ -214,6 +216,8 @@ v3.3.0版本开始支持配置数据删除时间段。
* task_pool_size，修补任务的并发度，默认10
* safe_delay_time_h，删除保护期，默认72h，如果配置负数则表示直接删除
* message_punish_threshold，惩罚阈值，如果对应消费失败次数超过该值，则会惩罚一段时间，避免短时间内大量重试，默认3次
* message_punish_time_m，惩罚时间，默认10分钟
* delete_log，删除日志保留目录，需要配置，chunkbits默认为29
* delete_hour_range，支持配置删除时间段，24小时制，比如以下配置表示凌晨1点到3点中间时间段才会发起删除请求，如果不配置默认全天删除
```json

4
docs/source/maintenance/configs/blobstore/scheduler.md
View File

@ -194,6 +194,8 @@ Starting from version v3.3.0, concurrent disk repair is supported.
### shard_repair
* task_pool_size, concurrency of repair tasks, default is 10
* message_punish_threshold, Punishment threshold, if the corresponding number of failed attempts to consume a message exceeds this value, a punishment will be imposed for a period of time to avoid excessive retries within a short period. The default value is 3.
* message_punish_time_m, punishment time, default 10 minutes
* orphan_shard_log, record information of orphan data repair failures, directory needs to be configured, chunkbits is the log file rotation size, default is 29 (2^29 bytes)
```json
{
@ -216,6 +218,8 @@ Starting from version v3.3.0, it is supported to configure the data deletion tim
* task_pool_size, concurrency of deletion tasks, default is 10
* safe_delay_time_h, deletion protection period, default is 72h. If a negative value is configured, the data will be deleted directly.
* message_punish_threshold, Punishment threshold, if the corresponding number of failed attempts to consume a message exceeds this value, a punishment will be imposed for a period of time to avoid excessive retries within a short period. The default value is 3.
* message_punish_time_m, punishment time, default 10 minutes
* delete_log, directory for storing deletion logs, needs to be configured, chunkbits default is 29
* delete_hour_range, supports configuring the deletion time period in 24-hour format. For example, the following configuration indicates that deletion requests will only be initiated during the time period between 1:00 a.m. and 3:00 a.m. If not configured, deletion will be performed all day.
```json