From 6fd299fc4a105e537b319f69ef1f472940a3802b Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Thu, 12 Aug 2021 15:14:35 +0800 Subject: [PATCH 01/12] pd-control: add new config of balance-hot-region-scheduler --- pd-control.md | 52 +++++++++++++++++++++++++++++++++++++++++++++------ 1 file changed, 46 insertions(+), 6 deletions(-) diff --git a/pd-control.md b/pd-control.md index fe003c7457ba6..e3e36b153feb3 100644 --- a/pd-control.md +++ b/pd-control.md @@ -720,30 +720,52 @@ Usage: { "min-hot-byte-rate": 100, "min-hot-key-rate": 10, + "min-hot-query-rate": 10, "max-zombie-rounds": 3, "max-peer-number": 1000, "byte-rate-rank-step-ratio": 0.05, "key-rate-rank-step-ratio": 0.05, + "query-rate-rank-step-ratio": 0.05, "count-rank-step-ratio": 0.01, "great-dec-ratio": 0.95, "minor-dec-ratio": 0.99, - "src-tolerance-ratio": 1.02, - "dst-tolerance-ratio": 1.02 + "src-tolerance-ratio": 1.05, + "dst-tolerance-ratio": 1.05, + "read-priorities": [ + "query", + "byte" + ], + "write-leader-priorities": [ + "key", + "byte" + ], + "write-peer-priorities": [ + "byte", + "key" + ], + "strict-picking-store": "true", + "enable-for-tiflash": "true" } ``` -- `min-hot-byte-rate` means the smallest byte counted, which is usually 100. +- `min-hot-byte-rate` means the smallest number byte counted, which is usually 100. ```bash >> scheduler config balance-hot-region-scheduler set min-hot-byte-rate 100 ``` -- `min-hot-key-rate` means the smallest key counted, which is usually 10. +- `min-hot-key-rate` means the smallest number key counted, which is usually 10. ```bash >> scheduler config balance-hot-region-scheduler set min-hot-key-rate 10 ``` +- `min-hot-query-rate` means the smallest number query counted, which is usually 10. + + ```bash + >> scheduler config balance-hot-region-scheduler set min-hot-query-rate 10 + ``` + - `max-zombie-rounds` means the maximum number of heartbeats with which an operator can be considered as the pending influence. If you set it to a larger value, more operators might be included in the pending influence. Usually, you do not need to adjust its value. Pending influence refers to the operator influence that is generated during scheduling but still has an effect. ```bash @@ -756,7 +778,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set max-peer-number 1000 ``` -- `byte-rate-rank-step-ratio`, `key-rate-rank-step-ratio`, and `count-rank-step-ratio` respectively mean the step ranks of byte, key, and count. The rank step ratio decides the step when the rank is calculated. `great-dec-ratio` and `minor-dec-ratio` are used to determine the `dec` rank. Usually, you do not need to modify these items. +- `byte-rate-rank-step-ratio`, `key-rate-rank-step-ratio`, `query-rate-rank-step-ratio`, and `count-rank-step-ratio` respectively mean the step ranks of byte, key, query, and count. The rank-step-ratio decides the step when the rank is calculated. `great-dec-ratio` and `minor-dec-ratio` are used to determine the `dec` rank. Usually, you do not need to modify these items. ```bash >> scheduler config balance-hot-region-scheduler set byte-rate-rank-step-ratio 0.05 @@ -765,7 +787,25 @@ Usage: - `src-tolerance-ratio` and `dst-tolerance-ratio` are configuration items for the expectation scheduler. The smaller the `tolerance-ratio`, the easier it is for scheduling. When redundant scheduling occurs, you can appropriately increase this value. ```bash - >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.05 + >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 + ``` + +- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hotspots are delt with. For hotspots of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hotspots of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations will not take effect, and the compatible configurations will be used. Usually, you do not need to modify these configuration items. + + ```bash + >> scheduler config balance-hot-region-scheduler set read-priorities query,byte + ``` + +- `strict-picking-store` is a switch that controls the search space of hotspot scheduling. When it is enabled and if stability is ensured, hotspot scheduling will start. Usually it is enabled. When it is disabled, only the balance of dimensions of the first priority is enusred, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. + + ```bash + >> scheduler config balance-hot-region-scheduler set strict-picking-store true + ``` + +- `enable-for-tiflash` is a switch that controls whether hotspot scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hotspot scheduling between TiFlash instances will not start. + + ```bash + >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true ``` ### `store [delete | label | weight | remove-tombstone | limit | limit-scene] [--jq=""]` From 053c5c22da4e5132da7687fed951d12cb76a54b5 Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Tue, 17 Aug 2021 17:02:52 +0800 Subject: [PATCH 02/12] address comments --- pd-control.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pd-control.md b/pd-control.md index e3e36b153feb3..b46ceb5a41af6 100644 --- a/pd-control.md +++ b/pd-control.md @@ -754,13 +754,13 @@ Usage: >> scheduler config balance-hot-region-scheduler set min-hot-byte-rate 100 ``` -- `min-hot-key-rate` means the smallest number key counted, which is usually 10. +- `min-hot-key-rate` means the smallest number of keys to be counted, which is usually 10. ```bash >> scheduler config balance-hot-region-scheduler set min-hot-key-rate 10 ``` -- `min-hot-query-rate` means the smallest number query counted, which is usually 10. +- `min-hot-query-rate` means the smallest number of queries to be counted, which is usually 10. ```bash >> scheduler config balance-hot-region-scheduler set min-hot-query-rate 10 From 9c51c1d7e91522699d81550528e643c941d96615 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Tue, 17 Aug 2021 17:03:27 +0800 Subject: [PATCH 03/12] Apply suggestions from code review Co-authored-by: lhy1024 --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index b46ceb5a41af6..e7af5b5f87f49 100644 --- a/pd-control.md +++ b/pd-control.md @@ -748,7 +748,7 @@ Usage: } ``` -- `min-hot-byte-rate` means the smallest number byte counted, which is usually 100. +- `min-hot-byte-rate` means the smallest number of bytes to be counted, which is usually 100. ```bash >> scheduler config balance-hot-region-scheduler set min-hot-byte-rate 100 From 0794cc20053f8817489cdff99a423b89490c17a8 Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Tue, 17 Aug 2021 17:50:47 +0800 Subject: [PATCH 04/12] fix typo --- pd-control.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pd-control.md b/pd-control.md index e7af5b5f87f49..11ad397f83266 100644 --- a/pd-control.md +++ b/pd-control.md @@ -790,7 +790,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 ``` -- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hotspots are delt with. For hotspots of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hotspots of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations will not take effect, and the compatible configurations will be used. Usually, you do not need to modify these configuration items. +- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hotspots are dealt with. For hotspots of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hotspots of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations do not take effect, and the compatible configurations are used. Usually, you do not need to modify these configuration items. ```bash >> scheduler config balance-hot-region-scheduler set read-priorities query,byte @@ -802,7 +802,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set strict-picking-store true ``` -- `enable-for-tiflash` is a switch that controls whether hotspot scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hotspot scheduling between TiFlash instances will not start. +- `enable-for-tiflash` is a switch that controls whether hotspot scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hotspot scheduling between TiFlash instances do not start. ```bash >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true From 77a2674e05830818a5c48ba289423083c4a057fa Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Tue, 17 Aug 2021 17:56:34 +0800 Subject: [PATCH 05/12] change hotspot to hot region --- pd-control.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pd-control.md b/pd-control.md index 11ad397f83266..41d2f535d1905 100644 --- a/pd-control.md +++ b/pd-control.md @@ -282,7 +282,7 @@ Usage: >> config set hot-region-schedule-limit 4 // 4 tasks of hot Region scheduling at the same time at most ``` -- `hot-region-cache-hits-threshold` is used to set the number of minutes required to identify a hot Region. PD can participate in the hotspot scheduling only after the Region is in the hotspot state for more than this number of minutes. +- `hot-region-cache-hits-threshold` is used to set the number of minutes required to identify a hot Region. PD can participate in the hot region scheduling only after the Region is in the hotspot state for more than this number of minutes. - `tolerant-size-ratio` controls the size of the balance buffer area. When the score difference between the leader or Region of the two stores is less than specified multiple times of the Region size, it is considered in balance by PD. @@ -790,19 +790,19 @@ Usage: >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 ``` -- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hotspots are dealt with. For hotspots of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hotspots of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations do not take effect, and the compatible configurations are used. Usually, you do not need to modify these configuration items. +- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hot regions are dealt with. For hot regions of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hot regions of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations do not take effect, and the compatible configurations are used. Usually, you do not need to modify these configuration items. ```bash >> scheduler config balance-hot-region-scheduler set read-priorities query,byte ``` -- `strict-picking-store` is a switch that controls the search space of hotspot scheduling. When it is enabled and if stability is ensured, hotspot scheduling will start. Usually it is enabled. When it is disabled, only the balance of dimensions of the first priority is enusred, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. +- `strict-picking-store` is a switch that controls the search space of hot region scheduling. When it is enabled and if stability is ensured, hot region scheduling will start. Usually it is enabled. When it is disabled, only the balance of dimensions of the first priority is enusred, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. ```bash >> scheduler config balance-hot-region-scheduler set strict-picking-store true ``` -- `enable-for-tiflash` is a switch that controls whether hotspot scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hotspot scheduling between TiFlash instances do not start. +- `enable-for-tiflash` is a switch that controls whether hot region scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hot region scheduling between TiFlash instances do not start. ```bash >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true From a204f2b032665cf4e3570ffb527accd4879fb51e Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Tue, 17 Aug 2021 18:00:55 +0800 Subject: [PATCH 06/12] fix typo --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index 41d2f535d1905..910790b359d5b 100644 --- a/pd-control.md +++ b/pd-control.md @@ -282,7 +282,7 @@ Usage: >> config set hot-region-schedule-limit 4 // 4 tasks of hot Region scheduling at the same time at most ``` -- `hot-region-cache-hits-threshold` is used to set the number of minutes required to identify a hot Region. PD can participate in the hot region scheduling only after the Region is in the hotspot state for more than this number of minutes. +- `hot-region-cache-hits-threshold` is used to set the number of minutes required to identify a hot Region. PD can participate in the hotspot scheduling only after the Region is in the hotspot state for more than this number of minutes. - `tolerant-size-ratio` controls the size of the balance buffer area. When the score difference between the leader or Region of the two stores is less than specified multiple times of the Region size, it is considered in balance by PD. From 6c83d38ba369ddc0fa3a09d8ef875d29a4af20c0 Mon Sep 17 00:00:00 2001 From: Xiaozhen Liu Date: Fri, 20 Aug 2021 16:03:42 +0800 Subject: [PATCH 07/12] translate https://github.com/pingcap/docs-cn/pull/6888/files. --- pd-control.md | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/pd-control.md b/pd-control.md index 910790b359d5b..434054a4669fd 100644 --- a/pd-control.md +++ b/pd-control.md @@ -790,19 +790,26 @@ Usage: >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 ``` -- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control the first and second dimensions which have the first priority of balance when different types of hot regions are dealt with. For hot regions of `read` and `write-leader` types, the available dimensions are `query`, `byte`, and `key`. For hot regions of `write-peer`, the available dimensions are `byte` and `key`. If not all the cluster components are upgraded to v5.2 and later, these configurations do not take effect, and the compatible configurations are used. Usually, you do not need to modify these configuration items. +- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control which dimensions have the priority for hot Region scheduling and support two dimensions. + + - `read-priorities` and `write-leader-priorities` control the dimensions to be prioritized for read and write-leader hot Region scheduling. The available dimensions are `query`, `byte` and `key`. + - `write-peer-priorities` controls the dimension to be prioritized for write-peer hot Region scheduling. The available dimensions are `byte` and `key`. + + > **Note:** + > + > If not all the cluster components are upgraded to v5.2 and later, the configuration of `query` dimension does not take effect. If some components are upgraded, the `byte` and `key` dimensions still by default have the priority for hot Region scheduling. If all the components of the cluster are upgraded to v5.2 and later, such a compatible configuration still takes effect. You can view the real-time configuration using `pd-ctl` command. Usually, you do not need to modify these configurations. ```bash >> scheduler config balance-hot-region-scheduler set read-priorities query,byte ``` -- `strict-picking-store` is a switch that controls the search space of hot region scheduling. When it is enabled and if stability is ensured, hot region scheduling will start. Usually it is enabled. When it is disabled, only the balance of dimensions of the first priority is enusred, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. +- `strict-picking-store` controls the search space of hot Region scheduling. Usually it is enabled. When it is enabled, hot Region scheduling ensures the balance between the two configured dimensions. When it is disabled, hot Region scheduling only ensures the balance of dimensions with the first priority, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. ```bash >> scheduler config balance-hot-region-scheduler set strict-picking-store true ``` -- `enable-for-tiflash` is a switch that controls whether hot region scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hot region scheduling between TiFlash instances do not start. +- `enable-for-tiflash` controls whether hot Region scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hot Region scheduling between TiFlash instances do not start. ```bash >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true From 46cd952a741efeecb4dc63a41cd654a6c0e280d5 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Fri, 20 Aug 2021 16:08:27 +0800 Subject: [PATCH 08/12] Apply suggestions from code review --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index 434054a4669fd..96ea686d16138 100644 --- a/pd-control.md +++ b/pd-control.md @@ -803,7 +803,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set read-priorities query,byte ``` -- `strict-picking-store` controls the search space of hot Region scheduling. Usually it is enabled. When it is enabled, hot Region scheduling ensures the balance between the two configured dimensions. When it is disabled, hot Region scheduling only ensures the balance of dimensions with the first priority, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration item. +- `strict-picking-store` controls the search space of hot Region scheduling. Usually it is enabled. When it is enabled, hot Region scheduling ensures the balance between the two configured dimensions. When it is disabled, hot Region scheduling only ensures the balance of dimensions with the first priority, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration. ```bash >> scheduler config balance-hot-region-scheduler set strict-picking-store true From 04f4e99f9ba69972088298714924aa78500d6185 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Fri, 20 Aug 2021 16:22:37 +0800 Subject: [PATCH 09/12] Apply suggestions from code review Co-authored-by: lhy1024 --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index 96ea686d16138..767bc978056c2 100644 --- a/pd-control.md +++ b/pd-control.md @@ -797,7 +797,7 @@ Usage: > **Note:** > - > If not all the cluster components are upgraded to v5.2 and later, the configuration of `query` dimension does not take effect. If some components are upgraded, the `byte` and `key` dimensions still by default have the priority for hot Region scheduling. If all the components of the cluster are upgraded to v5.2 and later, such a compatible configuration still takes effect. You can view the real-time configuration using `pd-ctl` command. Usually, you do not need to modify these configurations. + > If not all the cluster components are upgraded to v5.2 and later, the configuration of `query` dimension does not take effect. If some components are upgraded, the `byte` and `key` dimensions still by default have the priority for hot Region scheduling. After all the components of the cluster are upgraded to v5.2 and later, such a compatible configuration still takes effect. You can view the real-time configuration using `pd-ctl` command. Usually, you do not need to modify these configurations. ```bash >> scheduler config balance-hot-region-scheduler set read-priorities query,byte From d06e0d70b9579bfafae59f83bf6b97a029019fcf Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Fri, 20 Aug 2021 17:51:29 +0800 Subject: [PATCH 10/12] Apply suggestions from code review Co-authored-by: lhy1024 --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index 767bc978056c2..39833564997bc 100644 --- a/pd-control.md +++ b/pd-control.md @@ -809,7 +809,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set strict-picking-store true ``` -- `enable-for-tiflash` controls whether hot Region scheduling takes effect for TiFlash. Usually it is enabled. When it is disabled, the hot Region scheduling between TiFlash instances do not start. +- `enable-for-tiflash` controls whether hot Region scheduling takes effect for TiFlash instances. Usually it is enabled. When it is disabled, the hot Region scheduling between TiFlash instances do not start. ```bash >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true From d69e4cec73296b55c92d19919faf5cf0724a88ee Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Mon, 23 Aug 2021 15:52:10 +0800 Subject: [PATCH 11/12] Apply suggestions from code review Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> --- pd-control.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pd-control.md b/pd-control.md index 39833564997bc..337e5beb04ae5 100644 --- a/pd-control.md +++ b/pd-control.md @@ -787,17 +787,17 @@ Usage: - `src-tolerance-ratio` and `dst-tolerance-ratio` are configuration items for the expectation scheduler. The smaller the `tolerance-ratio`, the easier it is for scheduling. When redundant scheduling occurs, you can appropriately increase this value. ```bash - >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 + >> scheduler config balance-hot-region-scheduler set src-tolerance-ratio 1.1 ``` -- `read-priorities`,`write-leader-priorities`, and `write-peer-priorities` control which dimensions have the priority for hot Region scheduling and support two dimensions. +- `read-priorities`, `write-leader-priorities`, and `write-peer-priorities` control which dimension the scheduler prioritizes for hot Region scheduling. Two dimensions are supported for configuration. - - `read-priorities` and `write-leader-priorities` control the dimensions to be prioritized for read and write-leader hot Region scheduling. The available dimensions are `query`, `byte` and `key`. - - `write-peer-priorities` controls the dimension to be prioritized for write-peer hot Region scheduling. The available dimensions are `byte` and `key`. + - `read-priorities` and `write-leader-priorities` control which dimensions the scheduler prioritizes for scheduling hot Regions of the read and write-leader types. The dimension options are `query`, `byte`, and `key`. + - `write-peer-priorities` controls which dimensions the scheduler prioritizes for scheduling hot Regions of the write-peer type. The dimension options are `byte` and `key`. > **Note:** > - > If not all the cluster components are upgraded to v5.2 and later, the configuration of `query` dimension does not take effect. If some components are upgraded, the `byte` and `key` dimensions still by default have the priority for hot Region scheduling. After all the components of the cluster are upgraded to v5.2 and later, such a compatible configuration still takes effect. You can view the real-time configuration using `pd-ctl` command. Usually, you do not need to modify these configurations. + > If a cluster component is earlier than v5.2, the configuration of `query` dimension does not take effect. If some components are upgraded to v5.2 or later, the `byte` and `key` dimensions still by default have the priority for hot Region scheduling. After all components of the cluster are upgraded to v5.2 or later, such a configuration still takes effect for compatibility. You can view the real-time configuration using the `pd-ctl` command. Usually, you do not need to modify these configurations. ```bash >> scheduler config balance-hot-region-scheduler set read-priorities query,byte @@ -809,7 +809,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set strict-picking-store true ``` -- `enable-for-tiflash` controls whether hot Region scheduling takes effect for TiFlash instances. Usually it is enabled. When it is disabled, the hot Region scheduling between TiFlash instances do not start. +- `enable-for-tiflash` controls whether hot Region scheduling takes effect for TiFlash instances. Usually, it is enabled. When it is disabled, the hot Region scheduling between TiFlash instances is not performed. ```bash >> scheduler config balance-hot-region-scheduler set enable-for-tiflash true From fd2cf39b8c38ef7facaf38ee1f61e728a01b2c30 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Mon, 23 Aug 2021 16:07:07 +0800 Subject: [PATCH 12/12] Apply suggestions from code review Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> --- pd-control.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pd-control.md b/pd-control.md index 337e5beb04ae5..5c6ff795a75e7 100644 --- a/pd-control.md +++ b/pd-control.md @@ -803,7 +803,7 @@ Usage: >> scheduler config balance-hot-region-scheduler set read-priorities query,byte ``` -- `strict-picking-store` controls the search space of hot Region scheduling. Usually it is enabled. When it is enabled, hot Region scheduling ensures the balance between the two configured dimensions. When it is disabled, hot Region scheduling only ensures the balance of dimensions with the first priority, which might reduce the balance of other dimensions. Usually, you do not need to modify this configuration. +- `strict-picking-store` controls the search space of hot Region scheduling. Usually, it is enabled. When it is enabled, hot Region scheduling ensures hotspot balance on the two configured dimensions. When it is disabled, hot Region scheduling only ensures the balance on the dimension with the first priority, which might reduce balance on other dimensions. Usually, you do not need to modify this configuration. ```bash >> scheduler config balance-hot-region-scheduler set strict-picking-store true