IT mysql_test auto_increment failed

[jebter]

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

https://ci.pingcap.net/blue/organizations/jenkins/tidb_ghpr_common_test/detail/tidb_ghpr_common_test/9224/pipeline#step-394-log-455
[2022-03-25T00:52:12.741Z] time="2022-03-25T08:52:12+08:00" level=error msg="run test [auto_increment] err: sql:SHOW CREATE TABLE t1;: failed to run query \n"SHOW CREATE TABLE t1;" \n around line 443, \nwe need(325):\nSHOW CREATE TABLE t1;\nTable\tCreate Table\nt1\tCREATE TABLE t1 (\n t1_name varchar(255) DEFAULT NULL,\n t1_id int(10) unsigned NOT NULL AUTO_INCREMENT,\n PRIMARY KEY (t1_id) /*T![clustered_index] CLUSTERED */,\n KEY t1_name (t1_name)\n) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin AUTO_INCREMENT=2001000\nbut got(325):\nSHOW CREATE TABLE t1;\nTable\tCreate Table\nt1\tCREATE TABLE t1 (\n t1_name varchar(255) DEFAULT NULL,\n t1_id int(10) unsigned NOT NULL AUTO_INCREMENT,\n PRIMARY KEY (t1_id) /*T![clustered_index] CLUSTERED */,\n KEY t1_name (t1_name)\n) ENGINE=InnoDB DEFAULT CHARSET=latin1 COLLATE=latin1_bin AUTO_INCREMENT=601361\n\n"

2. What did you expect to see? (Required)

3. What did you see instead (Required)

4. What is your TiDB version? (Required)

[tangenta]

For auto_increment ID, the cached ID step is determined by the allocating rate. When the allocation is triggered in a short time, the step will be very large(the maximum is 2000000).

So if the test is run slowly, the step will be small(the minimum is 60000).

This is a defect of test, maybe we can improve it later.