Skip to content

troubleshoot-hot-spot-issues: remove allow-auto-random from config manual #4037

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomShawn merged 3 commits into from
Oct 13, 2020
Merged

troubleshoot-hot-spot-issues: remove allow-auto-random from config manual #4037

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
d258254
Remove allow-auto-random from config manual
Joyinqin Oct 13, 2020
4036da2
Merge branch 'master' into delete
TomShawn Oct 13, 2020
fca1b9a
Merge branch 'master' into delete
TomShawn Oct 13, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 0 additions & 9 deletions troubleshoot-hot-spot-issues.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down