From ef5d75439254caa26e1093c8d6f994b306247cbf Mon Sep 17 00:00:00 2001 From: lhy1024 <19542290+lhy1024@users.noreply.github.com> Date: Thu, 8 Oct 2026 09:31:49 +0800 Subject: [PATCH 1/5] table-affinity: clarify scheduling microservice version support Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com> --- table-affinity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/table-affinity.md b/table-affinity.md index f0a93e3daf973..e8c4871ba8d8e 100644 --- a/table-affinity.md +++ b/table-affinity.md @@ -17,7 +17,7 @@ When you enable PD affinity scheduling and set the `AFFINITY` option of a table Before using table-level data affinity, note the following limitations: -- This feature does not take effect in [PD Microservices Mode](/pd-microservices.md). +- In v8.5.5, this feature does not take effect when scheduling is handled by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). Starting from v8.5.6, affinity scheduling is available in this mode. - This feature does not work with [Temporary tables](/temporary-tables.md) and [views](/views.md). - After data affinity is configured for a [partitioned table](/partitioned-table.md), **modifying the table partitioning scheme is not supported**, including adding, dropping, reorganizing, or swapping partitions. To change the partitioning scheme, you must first remove the affinity configuration for that table. - **Evaluate disk capacity in advance for large data volumes**: after affinity is enabled, PD prioritizes scheduling Regions of a table or partition to the same subset of a few TiKV nodes. For tables or partitions with large data volumes, this might significantly increase disk usage on these nodes. It is recommended to evaluate disk capacity and monitor it in advance. From 40344f002b5c06777e2610b089d0b5d160b3a768 Mon Sep 17 00:00:00 2001 From: lhy1024 <19542290+lhy1024@users.noreply.github.com> Date: Thu, 8 Oct 2026 10:11:38 +0800 Subject: [PATCH 2/5] table-affinity: describe microservice support positively Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com> --- table-affinity.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/table-affinity.md b/table-affinity.md index e8c4871ba8d8e..c0c71e73a4b78 100644 --- a/table-affinity.md +++ b/table-affinity.md @@ -13,11 +13,12 @@ Table-level data affinity is a PD mechanism for scheduling data distribution at When you enable PD affinity scheduling and set the `AFFINITY` option of a table to `table` or `partition`, PD groups Regions belonging to the same table or partition into the same affinity group. During scheduling, PD prioritizes placing the Leader and Voter replicas of these Regions on the same subset of a few TiKV nodes. This reduces network latency caused by cross-node access during queries, thereby improving query performance. +Starting from v8.5.6 and v9.0.0, table-level data affinity supports scheduling by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). + ## Limitations Before using table-level data affinity, note the following limitations: -- In v8.5.5, this feature does not take effect when scheduling is handled by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). Starting from v8.5.6, affinity scheduling is available in this mode. - This feature does not work with [Temporary tables](/temporary-tables.md) and [views](/views.md). - After data affinity is configured for a [partitioned table](/partitioned-table.md), **modifying the table partitioning scheme is not supported**, including adding, dropping, reorganizing, or swapping partitions. To change the partitioning scheme, you must first remove the affinity configuration for that table. - **Evaluate disk capacity in advance for large data volumes**: after affinity is enabled, PD prioritizes scheduling Regions of a table or partition to the same subset of a few TiKV nodes. For tables or partitions with large data volumes, this might significantly increase disk usage on these nodes. It is recommended to evaluate disk capacity and monitor it in advance. From 43e2afaad29ca7d882d4dfd49ae13a3f721874ea Mon Sep 17 00:00:00 2001 From: lhy1024 <19542290+lhy1024@users.noreply.github.com> Date: Thu, 8 Oct 2026 10:16:17 +0800 Subject: [PATCH 3/5] table-affinity: use verified microservice support version Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com> --- table-affinity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/table-affinity.md b/table-affinity.md index c0c71e73a4b78..ae882b75abc49 100644 --- a/table-affinity.md +++ b/table-affinity.md @@ -13,7 +13,7 @@ Table-level data affinity is a PD mechanism for scheduling data distribution at When you enable PD affinity scheduling and set the `AFFINITY` option of a table to `table` or `partition`, PD groups Regions belonging to the same table or partition into the same affinity group. During scheduling, PD prioritizes placing the Leader and Voter replicas of these Regions on the same subset of a few TiKV nodes. This reduces network latency caused by cross-node access during queries, thereby improving query performance. -Starting from v8.5.6 and v9.0.0, table-level data affinity supports scheduling by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). +Starting from v8.5.6, table-level data affinity supports scheduling by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). ## Limitations From 1d64d5f0264a8cf72ead59379fce022162f31897 Mon Sep 17 00:00:00 2001 From: lhy1024 <19542290+lhy1024@users.noreply.github.com> Date: Thu, 8 Oct 2026 10:19:22 +0800 Subject: [PATCH 4/5] table-affinity: distinguish deployment mode support versions Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com> --- table-affinity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/table-affinity.md b/table-affinity.md index ae882b75abc49..2bcae2618a243 100644 --- a/table-affinity.md +++ b/table-affinity.md @@ -13,7 +13,7 @@ Table-level data affinity is a PD mechanism for scheduling data distribution at When you enable PD affinity scheduling and set the `AFFINITY` option of a table to `table` or `partition`, PD groups Regions belonging to the same table or partition into the same affinity group. During scheduling, PD prioritizes placing the Leader and Voter replicas of these Regions on the same subset of a few TiKV nodes. This reduces network latency caused by cross-node access during queries, thereby improving query performance. -Starting from v8.5.6, table-level data affinity supports scheduling by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). +Table-level data affinity is available in PD's classic deployment mode starting from v8.5.5. Starting from v8.5.6, it is also available when scheduling is handled by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). ## Limitations From e70d552cc8e7dba3ee7c458c6080e2bc4a7660ea Mon Sep 17 00:00:00 2001 From: lhy1024 <19542290+lhy1024@users.noreply.github.com> Date: Thu, 8 Oct 2026 12:50:53 +0800 Subject: [PATCH 5/5] table-affinity: correct microservice support version Signed-off-by: lhy1024 <19542290+lhy1024@users.noreply.github.com> --- table-affinity.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/table-affinity.md b/table-affinity.md index 2bcae2618a243..4b69a4175e5b0 100644 --- a/table-affinity.md +++ b/table-affinity.md @@ -13,7 +13,7 @@ Table-level data affinity is a PD mechanism for scheduling data distribution at When you enable PD affinity scheduling and set the `AFFINITY` option of a table to `table` or `partition`, PD groups Regions belonging to the same table or partition into the same affinity group. During scheduling, PD prioritizes placing the Leader and Voter replicas of these Regions on the same subset of a few TiKV nodes. This reduces network latency caused by cross-node access during queries, thereby improving query performance. -Table-level data affinity is available in PD's classic deployment mode starting from v8.5.5. Starting from v8.5.6, it is also available when scheduling is handled by the scheduling microservice in [PD Microservices Mode](/pd-microservices.md). +Table-level data affinity is available starting from v8.5.5 when PD is not deployed in [PD Microservices Mode](/pd-microservices.md). Starting from v8.5.7, it is also available in PD Microservices Mode when scheduling is handled by the scheduling microservice. ## Limitations