Inconsistency in Forge Sql Auto-increment column

Forge
1

I am using a primary key column defined like:
event_order BIGINT NOT NULL PRIMARY KEY AUTO_INCREMENT,

The ids are being auto generated something like this:
1, 2, 3, 30001, 4, 30002, 5, 6

It seems like two different number sequences are being interleaved. I would have expected the ids to be generated in numerical order like 1, 2, 3, 4, 5, 6, 7, 8. Is there any explanation for this? Is the database somehow pulling from two different sequences in the database? It seems like this would have a potential for a collision. Also, it makes it impossible for me to order the rows by id, because the id does not reflect the insertion order.

2

This is due to TiDB distributed database operation. Each shard or node of the database has a different cache or range of numbers it can use in the auto increment. Node 1 will have 1-30000, node two will have 30001-60000 etc. this means they don’t need to communicate when allocating a unique value.

See https://docs.pingcap.com/tidbcloud/auto-increment/#auto_increment

if you need a sequence of values etc you may need a different solution, see Unique Serial Number Generation