From c2fa7929e533f5dd047e9238deacb981c50bcf06 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 19 Jun 2025 17:43:24 +0800 Subject: [PATCH 1/6] Add temp.md --- temp.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 temp.md diff --git a/temp.md b/temp.md new file mode 100644 index 0000000000000..af27ff4986a7b --- /dev/null +++ b/temp.md @@ -0,0 +1 @@ +This is a test file. \ No newline at end of file From 2700b4f4edd3d79cecaed389a00eb68fe5703a52 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 19 Jun 2025 17:43:28 +0800 Subject: [PATCH 2/6] Delete temp.md --- temp.md | 1 - 1 file changed, 1 deletion(-) delete mode 100644 temp.md diff --git a/temp.md b/temp.md deleted file mode 100644 index af27ff4986a7b..0000000000000 --- a/temp.md +++ /dev/null @@ -1 +0,0 @@ -This is a test file. \ No newline at end of file From 07695b88489672d5e40833b12c0b10fc95c63171 Mon Sep 17 00:00:00 2001 From: Test User Date: Fri, 20 Jun 2025 09:24:06 +0800 Subject: [PATCH 3/6] add translation --- dynamic-config.md | 21 ++++++++++++++++++++- pd-configuration-file.md | 6 ++++++ 2 files changed, 26 insertions(+), 1 deletion(-) diff --git a/dynamic-config.md b/dynamic-config.md index 3c5af1ff84e82..4eeed5d5577e0 100644 --- a/dynamic-config.md +++ b/dynamic-config.md @@ -282,11 +282,11 @@ The following PD configuration items can be modified dynamically: | `schedule.max-merge-region-size` | Controls the size limit of `Region Merge` (in MiB) | | `schedule.max-merge-region-keys` | Specifies the maximum numbers of the `Region Merge` keys | | `schedule.patrol-region-interval` | Determines the frequency at which the checker inspects the health state of a Region | -| `scheduler.patrol-region-worker-count` | Controls the number of concurrent operators created by the checker when inspecting the health state of a Region | | `schedule.split-merge-interval` | Determines the time interval of performing split and merge operations on the same Region | | `schedule.max-snapshot-count` | Determines the maximum number of snapshots that a single store can send or receive at the same time | | `schedule.max-pending-peer-count` | Determines the maximum number of pending peers in a single store | | `schedule.max-store-down-time` | The downtime after which PD judges that the disconnected store cannot be recovered | +| `schedule.max-store-preparing-time` | Controls the maximum waiting time for the store to go online | | `schedule.leader-schedule-policy` | Determines the policy of Leader scheduling | | `schedule.leader-schedule-limit` | The number of Leader scheduling tasks performed at the same time | | `schedule.region-schedule-limit` | The number of Region scheduling tasks performed at the same time | @@ -304,16 +304,35 @@ The following PD configuration items can be modified dynamically: | `schedule.enable-location-replacement` | Determines whether to enable isolation level check | | `schedule.enable-cross-table-merge` | Determines whether to enable cross-table merge | | `schedule.enable-one-way-merge` | Enables one-way merge, which only allows merging with the next adjacent Region | +| `schedule.region-score-formula-version` | Controls the version of the Region score formula | +| `schedule.scheduler-max-waiting-operator` | Controls the number of waiting operators in each scheduler | +| `schedule.enable-debug-metrics` | Enables the metrics for debugging | +| `schedule.enable-heartbeat-concurrent-runner` | Enables asynchronous concurrent processing for Region heartbeats | +| `schedule.enable-heartbeat-breakdown-metrics` | Enables breakdown metrics for Region heartbeats to measure the time consumed in each stage of Region heartbeat processing | +| `schedule.enable-joint-consensus` | Controls whether to use Joint Consensus for replica scheduling | +| `schedule.hot-regions-write-interval` | The time interval at which PD stores hot Region information | +| `schedule.hot-regions-reserved-days` | Specifies how many days the hot Region information is retained | +| `schedule.max-movable-hot-peer-size` | Controls the maximum Region size that can be scheduled for hot Region scheduling. | +| `schedule.store-limit-version` | Controls the version of the store limit formula | +| `schedule.patrol-region-worker-count` | Controls the number of concurrent operators created by the checker when inspecting the health state of a Region | | `replication.max-replicas` | Sets the maximum number of replicas | | `replication.location-labels` | The topology information of a TiKV cluster | | `replication.enable-placement-rules` | Enables Placement Rules | | `replication.strictly-match-label` | Enables the label check | +| `replication.isolation-level` | The minimum topological isolation level of a TiKV cluster | | `pd-server.use-region-storage` | Enables independent Region storage | | `pd-server.max-gap-reset-ts` | Sets the maximum interval of resetting timestamp (BR) | | `pd-server.key-type` | Sets the cluster key type | | `pd-server.metric-storage` | Sets the storage address of the cluster metrics | | `pd-server.dashboard-address` | Sets the dashboard address | | `replication-mode.replication-mode` | Sets the backup mode | +| `replication-mode.dr-auto-sync.label-key` | Distinguishes different AZs and needs to match Placement Rules | +| `replication-mode.dr-auto-sync.primary` | The primary AZ | +| `replication-mode.dr-auto-sync.dr` | The disaster recovery (DR) AZ | +| `replication-mode.dr-auto-sync.primary-replicas` | The number of Voter replicas in the primary AZ | +| `replication-mode.dr-auto-sync.wait-store-timeout` | The waiting time for switching to asynchronous replication mode when network isolation or failure occurs | +| `replication-mode.dr-auto-sync.wait-recover-timeout` | The waiting time for switching back to the `sync-recover` status after the network recovers | +| `replication-mode.dr-auto-sync.pause-region-split` | Controls whether to pause Region split operations in the `async_wait` and `async` statuses | For detailed parameter description, refer to [PD Configuration File](/pd-configuration-file.md). diff --git a/pd-configuration-file.md b/pd-configuration-file.md index e57656ee7bafa..50b66d9b5b4d6 100644 --- a/pd-configuration-file.md +++ b/pd-configuration-file.md @@ -311,6 +311,12 @@ Configuration items related to scheduling + Controls the time interval between the `split` and `merge` operations on the same Region. That means a newly split Region will not be merged for a while. + Default value: `1h` +### `max-movable-hot-peer-size` New in v7.5.0 + ++ Controls the maximum Region size that can be scheduled for hot Region scheduling. ++ Default value: `512` ++ Unit: MiB + ### `max-snapshot-count` + Controls the maximum number of snapshots that a single store receives or sends at the same time. PD schedulers depend on this configuration to prevent the resources used for normal traffic from being preempted. From 0ecac620c302b97652ee361d3d15cb58ee8c1fa0 Mon Sep 17 00:00:00 2001 From: Test User Date: Fri, 20 Jun 2025 09:24:20 +0800 Subject: [PATCH 4/6] Update dynamic-config.md --- dynamic-config.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/dynamic-config.md b/dynamic-config.md index 4eeed5d5577e0..bb45499e65f08 100644 --- a/dynamic-config.md +++ b/dynamic-config.md @@ -325,11 +325,18 @@ The following PD configuration items can be modified dynamically: | `pd-server.key-type` | Sets the cluster key type | | `pd-server.metric-storage` | Sets the storage address of the cluster metrics | | `pd-server.dashboard-address` | Sets the dashboard address | +| `pd-server.flow-round-by-digit` | Specifies the number of lowest digits to round for the Region flow information | +| `pd-server.min-resolved-ts-persistence-interval` | Determines the interval at which the minimum resolved timestamp is persistent to the PD | +| `pd-server.server-memory-limit` | The memory limit ratio for a PD instance | +| `pd-server.server-memory-limit-gc-trigger` | The threshold ratio at which PD tries to trigger GC | +| `pd-server.enable-gogc-tuner` | Controls whether to enable the GOGC Tuner | +| `pd-server.gc-tuner-threshold` | The maximum memory threshold ratio for tuning GOGC | | `replication-mode.replication-mode` | Sets the backup mode | | `replication-mode.dr-auto-sync.label-key` | Distinguishes different AZs and needs to match Placement Rules | | `replication-mode.dr-auto-sync.primary` | The primary AZ | | `replication-mode.dr-auto-sync.dr` | The disaster recovery (DR) AZ | | `replication-mode.dr-auto-sync.primary-replicas` | The number of Voter replicas in the primary AZ | +| `replication-mode.dr-auto-sync.dr-replicas` | The number of Voter replicas in the disaster recovery (DR) AZ | | `replication-mode.dr-auto-sync.wait-store-timeout` | The waiting time for switching to asynchronous replication mode when network isolation or failure occurs | | `replication-mode.dr-auto-sync.wait-recover-timeout` | The waiting time for switching back to the `sync-recover` status after the network recovers | | `replication-mode.dr-auto-sync.pause-region-split` | Controls whether to pause Region split operations in the `async_wait` and `async` statuses | From 9bdc08449a49be17e26684ca7a5eb626d23e2298 Mon Sep 17 00:00:00 2001 From: Test User Date: Fri, 20 Jun 2025 09:30:30 +0800 Subject: [PATCH 5/6] Update dynamic-config.md --- dynamic-config.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/dynamic-config.md b/dynamic-config.md index bb45499e65f08..c4098dcd31187 100644 --- a/dynamic-config.md +++ b/dynamic-config.md @@ -313,7 +313,7 @@ The following PD configuration items can be modified dynamically: | `schedule.hot-regions-write-interval` | The time interval at which PD stores hot Region information | | `schedule.hot-regions-reserved-days` | Specifies how many days the hot Region information is retained | | `schedule.max-movable-hot-peer-size` | Controls the maximum Region size that can be scheduled for hot Region scheduling. | -| `schedule.store-limit-version` | Controls the version of the store limit formula | +| `schedule.store-limit-version` | Controls the version of [store limit](/configure-store-limit.md) | | `schedule.patrol-region-worker-count` | Controls the number of concurrent operators created by the checker when inspecting the health state of a Region | | `replication.max-replicas` | Sets the maximum number of replicas | | `replication.location-labels` | The topology information of a TiKV cluster | From 53c5cae418705df9745bc90631399d46070a27c8 Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Fri, 20 Jun 2025 14:29:55 +0800 Subject: [PATCH 6/6] Update pd-configuration-file.md --- pd-configuration-file.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-configuration-file.md b/pd-configuration-file.md index 50b66d9b5b4d6..5ff6c48222489 100644 --- a/pd-configuration-file.md +++ b/pd-configuration-file.md @@ -311,7 +311,7 @@ Configuration items related to scheduling + Controls the time interval between the `split` and `merge` operations on the same Region. That means a newly split Region will not be merged for a while. + Default value: `1h` -### `max-movable-hot-peer-size` New in v7.5.0 +### `max-movable-hot-peer-size` New in v6.1.0 + Controls the maximum Region size that can be scheduled for hot Region scheduling. + Default value: `512`