MySQL · 答疑释惑· InnoDB丢失自增值 · 数据库内核月报

**背景** 在上一期的月报中，我们在[InnoDB自增列重复值问题](http://mysql.taobao.org/index.php/MySQL%E5%86%85%E6%A0%B8%E6%9C%88%E6%8A%A5_2015.01#MySQL_.C2.B7_.E6.8D.89.E8.99.AB.E5.8A.A8.E6.80.81.C2.B7_InnoDB.E8.87.AA.E5.A2.9E.E5.88.97.E9.87.8D.E5.A4.8D.E5.80.BC.E9.97.AE.E9.A2.98) 中提到，InnoDB 自增列在重启后会丢失，因为MySQL没有持久化自增值，平时是存在内存表对象中的。如果实例重启的话，内存值丢失，其初始化过程是做了一个类似 select max(id) + 1 操作。实际上存在另外一种场景，实例即使不重启，也会导致自增值丢失。 **问题说明** 实例运行过种中，InnoDB表自增值是存储在表对象中的，表对象又是放在缓存中的，如果表太多而不能全部放在缓存中的话，老的表就会被置换出来，这种被置换出来的表下次再使用的时候，就要重新打开一遍，对自增列来说，这个过程就和实例重启类似，需要 select max(id) + 1 算一下自增值。对InnoDB来说，其数据字典中表对象缓存大小由 [table_definition_cache](http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_table_definition_cache) 系统变量控制，在5.6.8之后，其最小值是400。和表缓存相关的另一个系统变量是[table_open_cache](http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.html#sysvar_table_definition_cache)，这个控制的是所有线程打开表的缓存大小，这个缓存放在server层。下面我们用testcase的方式来给出InnoDB表对象对置换出的场景： ~~~ ##把 table_definition_cache 和 table_open_cache 都设为400 SET GLOBAL table_definition_cache = 400; SET GLOBAL table_open_cache = 400; ## 创建500个InnoDB自增表，各插入一条数据，然后把自增改为100 let $i=0; while($i < 500) { --eval CREATE TABLE t$i(id INT NOT NULL AUTO_INCREMENT, name VARCHAR(30), PRIMARY KEY(id)) ENGINE=InnoDB; --eval INSERT INTO t$i(name) VALUES("InnoDB"); --eval ALTER TABLE t$i AUTO_INCREMENT = 100; --inc $i } ## 最后400张表扫一遍 let $i=100; while($i < 500) { --eval SELECT * FROM t$i; --inc $i } ## 稍微sleep下，等mysqld把不用的表（t0..t99）换出 sleep 5; ## 查看t1表自增 SHOW CREATE TABLE t1; Table Create Table t1 CREATE TABLE `t1` ( `id` int(11) NOT NULL AUTO_INCREMENT, `name` varchar(30) DEFAULT NULL, PRIMARY KEY (`id`) ) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=latin1 ... ~~~ 可以看到自增值确实和重启场景一样，本应是100，却变成了 2（select max(id) + 1）了。 **问题分析** 原因就是缓存不够，导致表对象被换出，下次再用就要重新打开，这里给出调用栈，对代码感兴趣的同学可以看下。将老的table置换出： ~~~ #0 dict_table_remove_from_cache_low (table=0x2b81d054e278, lru_evict=1) at /path/to/mysql/storage/innobase/dict/dict0dict.cc:1804 #1 0x00000000011cf246 in dict_make_room_in_cache (max_tables=400, pct_check=100) at /path/to/mysql/storage/innobase/dict/dict0dict.cc:1261 #2 0x0000000001083564 in srv_master_evict_from_table_cache (pct_check=100) at /path/to/mysql/storage/innobase/srv/srv0srv.cc:2017 #3 0x0000000001084022 in srv_master_do_idle_tasks () at /path/to/mysql/storage/innobase/srv/srv0srv.cc:2212 #4 0x000000000108484a in srv_master_thread (arg=0x0) at /path/to/mysql/storage/innobase/srv/srv0srv.cc:2360 #5 0x00000030cc007851 in start_thread () from /lib64/libpthread.so.0 #6 0x00000030cbce767d in clone () from /lib64/libc.so.6 ~~~ 尝试从缓存加载表对象： ~~~ #0 dict_table_check_if_in_cache_low (table_name=0x2adef847db20 "test/t1") at /path/to/mysql/storage/innobase/include/dict0priv.ic:114 #1 0x00000000011cd51a in dict_table_open_on_name (table_name=0x2adef847db20 "test/t1", dict_locked=0, try_drop=1, ignore_err=DICT_ERR_IGNORE_NONE) at /path/to/mysql/storage/innobase/dict/dict0dict.cc:947 #2 0x0000000000e58d8a in ha_innobase::open (this=0x2adef9747010, name=0x2adef7460780 "./test/t1", mode=2, test_if_locked=2) at /path/to/mysql/storage/innobase/handler/ha_innodb.cc:4776 #3 0x000000000068668b in handler::ha_open (this=0x2adef9747010, table_arg=0x2adef742bc00, name=0x2adef7460780 "./test/t1", mode=2, test_if_locked=2) at /path/to/mysql/sql/handler.cc:2525 ... #9 0x00000000009c2a84 in mysqld_show_create (thd=0x2adef47aa000, table_list=0x2adef74200f0) at /path/to/mysql/sql/sql_show.cc:867 #10 0x00000000009553b1 in mysql_execute_command (thd=0x2adef47aa000) at /path/to/mysql/sql/sql_parse.cc:3507 #11 0x0000000000963bbe in mysql_parse (thd=0x2adef47aa000, rawbuf=0x2adef7420010 "show create table t1", length=20, parser_state=0x2adef8480630) at /path/to/mysql/sql/sql_parse.cc:6623 ... ~~~ 缓存加载不到表对象，用select maxt 逻辑初始化自增： ~~~ #0 row_search_max_autoinc (index=0x2b241d8f50f8, col_name=0x2b241d855519 "id", value=0x2b241e87d8a8) at /path/to/mysql/storage/innobase/row/row0sel.cc:5361 #1 0x0000000000e58998 in ha_innobase::innobase_initialize_autoinc (this=0x2b241fbd9010) at /path/to/mysql/storage/innobase/handler/ha_innodb.cc:4663 #2 0x0000000000e59bd9 in ha_innobase::open (this=0x2b241fbd9010, name=0x2b241d853780 "./test/t1", mode=2, test_if_locked=2) at /path/to/mysql/storage/innobase/handler/ha_innodb.cc:5089 #3 0x000000000068668b in handler::ha_open (this=0x2b241fbd9010, table_arg=0x2b241e422000, name=0x2b241d853780 "./test/t1", mode=2, test_if_locked=2) at /path/to/mysql/sql/handler.cc:2525 ... #9 0x00000000009c2a84 in mysqld_show_create (thd=0x2b241abaa000, table_list=0x2b241d8200f0) at /path/to/mysql/sql/sql_show.cc:867 #10 0x00000000009553b1 in mysql_execute_command (thd=0x2b241abaa000) at /path/to/mysql/sql/sql_parse.cc:3507 #11 0x0000000000963bbe in mysql_parse (thd=0x2b241abaa000, rawbuf=0x2b241d820010 "show create table t1", length=20, parser_state=0x2b241e880630) at /path/to/mysql/sql/sql_parse.cc:6623 ... ~~~ **处理建议** 对于这个问题，一种解决方法是从源码改进，将自增值持久化，可以参考[上期的月报](http://mysql.taobao.org/index.php/MySQL%E5%86%85%E6%A0%B8%E6%9C%88%E6%8A%A5_2015.01#MySQL_.C2.B7_.E6.8D.89.E8.99.AB.E5.8A.A8.E6.80.81.C2.B7_InnoDB.E8.87.AA.E5.A2.9E.E5.88.97.E9.87.8D.E5.A4.8D.E5.80.BC.E9.97.AE.E9.A2.98)给出的思路；如果不想改代码的话，可以这样绕过：在设定auto_increment值后，主动插入一行记录，这样不论在重启还是缓存淘汰的情况下，重新打开表仍能得到预期的值。