From d2a5c6ca67d24db862afb7bf0261650c913c47ce Mon Sep 17 00:00:00 2001 From: JoyinQ <56883733+Joyinqin@users.noreply.github.com> Date: Tue, 13 Oct 2020 13:44:48 +0800 Subject: [PATCH] cherry pick #4037 to release-4.0 Signed-off-by: ti-srebot --- troubleshoot-hot-spot-issues.md | 9 --------- 1 file changed, 9 deletions(-) diff --git a/troubleshoot-hot-spot-issues.md b/troubleshoot-hot-spot-issues.md index 515351605c448..d9ecf2e6dd566 100644 --- a/troubleshoot-hot-spot-issues.md +++ b/troubleshoot-hot-spot-issues.md @@ -120,15 +120,6 @@ As shown in the load diagrams above, before setting `SHARD_ROW_ID_BITS`, load ho To resolve the write hotspots brought by auto-increment primary keys, use `AUTO_RANDOM` to handle hotspot tables that have auto-increment primary keys. -> **Note:** -> -> Currently, this is an experimental feature, so it is not recommended to use it in the production environment. To enable this feature, use the following configuration: -> -> ``` -> [experimental] -> allow-auto-random = true -> ``` - If this feature is enabled, TiDB generates randomly distributed and non-repeated (before the space is used up) primary keys to achieve the purpose of scattering write hotspots. Note that the primary keys generated by TiDB are no longer auto-increment primary keys and you can use `LAST_INSERT_ID()` to obtain the primary key value assigned last time.