Bug #75110 | Massive, to-be-compressed not committed InnoDB table is total database downtime | ||
---|---|---|---|
Submitted: | 5 Dec 2014 1:02 | Modified: | 5 Dec 2014 12:32 |
Reporter: | Jouni Järvinen | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | OS: | Any | |
Assigned to: | CPU Architecture: | Any |
[5 Dec 2014 1:02]
Jouni Järvinen
[5 Dec 2014 11:53]
MySQL Verification Team
Hello Jouni Järvinen, Thank you for the report. Imho this behavior is by design and hence not a bug, please see http://dev.mysql.com/doc/refman/5.6/en/server-shutdown.html Also, it is not recommended to have such big transactions(per your note 50-60GB ). I would recommend you to take a look at available options such as innodb_fast_shutdown etc explained here http://dev.mysql.com/doc/refman/5.6/en/innodb-parameters.html#sysvar_innodb_fast_shutdown Thanks, Umesh
[5 Dec 2014 12:32]
Jouni Järvinen
I know it's by design and not a bug. I also have that setting disabled so there's less chances of data loss, as much as I don't like it.