Bug #39951 | Falcon: crash during crash recovery | ||
---|---|---|---|
Submitted: | 9 Oct 2008 11:23 | Modified: | 9 Jan 2009 14:09 |
Reporter: | Alexey Stroganov | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Falcon storage engine | Severity: | S1 (Critical) |
Version: | 6.0.7, 6.0-falcon.06.10.08 | OS: | Any |
Assigned to: | Vladislav Vaintroub | CPU Architecture: | Any |
Tags: | F_RECOVERY |
[9 Oct 2008 11:23]
Alexey Stroganov
[13 Oct 2008 21:03]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/commits/56151 2862 Vladislav Vaintroub 2008-10-13 Bug#39951 Falcon: crash during crash recovery. The problem is that in Database destructor, tables are accessed deep in systemConnection->rollback(), at the time all Table objects have been freed. Crash reason is accessing freed memory. Solution is to cleanup system connection before Table objects are freed.
[13 Oct 2008 21:46]
Vladislav Vaintroub
This particular patch fixes only this particular crash. Anything else (like the rest of recovery problems) is not subject of this patch.
[28 Oct 2008 8:10]
Bugs System
Pushed into 6.0.8-alpha (revid:vvaintroub@mysql.com-20081013210224-soy6yyyud2bq6wol) (version source revid:vvaintroub@mysql.com-20081013210224-soy6yyyud2bq6wol) (pib:5)
[9 Jan 2009 14:09]
MC Brown
A note has been added to the 6.0.8 changelog: MySQL may crash during the recover of Falcon tables if the server was shutdown after a large data load.