From 024ef9ffa51f075b89372d9436ad44288c7c6177 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Wed, 4 Aug 2021 18:28:02 +0800 Subject: [PATCH 1/3] add notice about scaling in pd node --- scale-tidb-using-tiup.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md index 7d82309f88876..cf4c9a750f99c 100644 --- a/scale-tidb-using-tiup.md +++ b/scale-tidb-using-tiup.md @@ -246,6 +246,10 @@ If you want to remove a TiKV node from the `10.0.1.5` host, take the following s > > You can take similar steps to remove the TiDB and PD node. +> **Note:** +> +> The PD Client in TiKV caches the list of PD nodes. The current version of TiKV has a mechanism to automatically and regularly update PD nodes, which can help avoid that the list of PD nodes cached by TiKV is old. However, after expanding new PD, you should try to avoid directly shrinking all PD nodes existing before the expansion. If necessary, before making all the previously existing PD nodes offline, make sure to switch the PD leader to the newly expanded PD nodes. + 1. View the node ID information: {{< copyable "shell-regular" >}} From 4bbde01c1b76207b296be521f0c9950d641760a5 Mon Sep 17 00:00:00 2001 From: TomShawn <41534398+TomShawn@users.noreply.github.com> Date: Thu, 5 Aug 2021 18:57:41 +0800 Subject: [PATCH 2/3] Update scale-tidb-using-tiup.md Co-authored-by: Allen Zhong --- scale-tidb-using-tiup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md index cf4c9a750f99c..5602ce61017f2 100644 --- a/scale-tidb-using-tiup.md +++ b/scale-tidb-using-tiup.md @@ -248,7 +248,7 @@ If you want to remove a TiKV node from the `10.0.1.5` host, take the following s > **Note:** > -> The PD Client in TiKV caches the list of PD nodes. The current version of TiKV has a mechanism to automatically and regularly update PD nodes, which can help avoid that the list of PD nodes cached by TiKV is old. However, after expanding new PD, you should try to avoid directly shrinking all PD nodes existing before the expansion. If necessary, before making all the previously existing PD nodes offline, make sure to switch the PD leader to the newly expanded PD nodes. +> The PD Client in TiKV caches the list of PD nodes. The current version of TiKV has a mechanism to automatically and regularly update PD nodes, which can help avoid that the list of PD nodes cached by TiKV is expired. However, after expanding new PD, you should try to avoid directly shrinking all PD nodes existing before the expansion. If necessary, before making all the previously existing PD nodes offline, make sure to switch the PD leader to the newly expanded PD nodes. 1. View the node ID information: From 804c3e2ebc0cd2e4c007ed6142e69cf20c156444 Mon Sep 17 00:00:00 2001 From: Liuxiaozhen12 <82579298+Liuxiaozhen12@users.noreply.github.com> Date: Thu, 5 Aug 2021 19:36:18 +0800 Subject: [PATCH 3/3] Update scale-tidb-using-tiup.md Co-authored-by: TomShawn <41534398+TomShawn@users.noreply.github.com> --- scale-tidb-using-tiup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/scale-tidb-using-tiup.md b/scale-tidb-using-tiup.md index 5602ce61017f2..bf6c1eda0fa04 100644 --- a/scale-tidb-using-tiup.md +++ b/scale-tidb-using-tiup.md @@ -248,7 +248,7 @@ If you want to remove a TiKV node from the `10.0.1.5` host, take the following s > **Note:** > -> The PD Client in TiKV caches the list of PD nodes. The current version of TiKV has a mechanism to automatically and regularly update PD nodes, which can help avoid that the list of PD nodes cached by TiKV is expired. However, after expanding new PD, you should try to avoid directly shrinking all PD nodes existing before the expansion. If necessary, before making all the previously existing PD nodes offline, make sure to switch the PD leader to the newly expanded PD nodes. +> The PD Client in TiKV caches the list of PD nodes. The current version of TiKV has a mechanism to automatically and regularly update PD nodes, which can help mitigate the issue of an expired list of PD nodes cached by TiKV. However, after scaling out PD, you should try to avoid directly removing all PD nodes at once that exist before the scaling. If necessary, before making all the previously existing PD nodes offline, make sure to switch the PD leader to a newly added PD node. 1. View the node ID information: