Bug #70396 | the server was crashed while running 5.7.2 on the dataset of 5.6.14 | ||
---|---|---|---|
Submitted: | 22 Sep 2013 10:44 | Modified: | 21 Feb 2014 12:04 |
Reporter: | zhai weixiang (OCA) | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S3 (Non-critical) |
Version: | 5.7.2 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[22 Sep 2013 10:44]
zhai weixiang
[22 Sep 2013 11:07]
MySQL Verification Team
Did you first do a 'slow shutdown' of innodb in 5.6.14 ? If not, please do it. on 5.6.14, SET GLOBAL innodb_fast_shutdown=0; Then shutdown and try starting 5.7.2.
[22 Sep 2013 11:20]
MySQL Verification Team
internally we had similar bug once. Bug 16819011 - CRASHING WHEN TRYING TO SHUTDOWN 5.7 SERVER STARTED WITH 5.6 DATA DIRECTORY
[22 Sep 2013 11:34]
zhai weixiang
I just killed MySQL5.6.14 (using kill -9 ) and restarted it using the mysqld of 5.7.2...
[22 Sep 2013 11:54]
MySQL Verification Team
Ok. I can repeat it after applying some pressure. In order to perform an upgrade, I try recommend *slow* shutdown. But, in most cases a normal shutdown will work fine. A crash recovery+upgrade/download at same time is not a supported or tested combination. Our MEB customers had this dilemma, it should be documented in the docs. ------------ InnoDB: Assertion failure in thread 35268 in file trx0rseg.cc line 133 InnoDB: Failing assertion: UT_LIST_GET_LEN(rseg->update_undo_list) == 0 InnoDB: We intentionally generate a memory trap. mysqld.exe!my_sigabrt_handler()[my_thr_init.c:447] mysqld.exe!raise()[winsig.c:593] mysqld.exe!abort()[abort.c:81] mysqld.exe!trx_rseg_mem_free()[trx0rseg.cc:134] mysqld.exe!trx_sys_close()[trx0sys.cc:1285] mysqld.exe!innobase_shutdown_for_mysql()[srv0start.cc:2566] mysqld.exe!innobase_end()[ha_innodb.cc:3269] mysqld.exe!ha_finalize_handlerton()[handler.cc:610] mysqld.exe!plugin_deinitialize()[sql_plugin.cc:928] mysqld.exe!reap_plugins()[sql_plugin.cc:1006] mysqld.exe!plugin_shutdown()[sql_plugin.cc:1699] mysqld.exe!clean_up()[mysqld.cc:1597] mysqld.exe!unireg_abort()[mysqld.cc:1491] mysqld.exe!init_server_components()[mysqld.cc:4235] mysqld.exe!win_main()[mysqld.cc:4730] mysqld.exe!mysql_service()[mysqld.cc:5028] mysqld.exe!mysqld_main()[mysqld.cc:5225] mysqld.exe!__tmainCRTStartup()[crt0.c:278] ------------
[23 Sep 2013 6:09]
MySQL Verification Team
I will set this report to 'Verified' because I could repeat it, and also want the contents documented internally. But, please don't be startled if it get rejected later..
[21 Feb 2014 12:04]
MySQL Verification Team
I cannot repeat this again using 5.6.17 and 5.7.4. If you see it on recent versions, kindly re-open this bug.