Support invalidating all auto_id cache in TiDB-server through HTTP API

tangenta commented 3 years ago

Feature Request

Is your feature request related to a problem? Please describe:

Related to #24122. This is a less automatic approach to solve the cache issue.

Describe the feature you'd like:

http://{TiDB_addr}:{status_port}/schema/cache_ids

This API only accepts the DELETE method and it will reset all the allocators in the TiDB server to drop cache IDs.

Describe alternatives you've considered:

Auto retry the transaction as described in #24122, but it is considered to be risky.
Alter each table increment-id one by one, but this is neither atomic nor convenient.

Teachability, Documentation, Adoption, Migration Strategy:

siddontang commented 3 years ago

I think invalidate_ids is an anti-restful mode.

BTW, have we already had a SQL interface for operating IDs?

tangenta commented 3 years ago

I think invalidate_ids is an anti-restful mode.

Updated. Now it should be more restful:)

a SQL interface for operating IDs?

We do have:

alter table `t` auto_increment = 10086;

However this SQL only affects one table at a time, what we need is an API that affects the whole TiDB server.