[MDEV-5621] Server random crash on ALTER TABLE Created: 2014-02-06 Updated: 2014-09-12 Resolved: 2014-09-12 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | None |
| Affects Version/s: | 5.5.35 |
| Fix Version/s: | 5.5.40 |
| Type: | Bug | Priority: | Major |
| Reporter: | azurit | Assignee: | Jan Lindström (Inactive) |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | alter, assertion, crash | ||
| Environment: |
Debian Wheezy, 64bit, Intel Xeon E5620, 4 GB RAM |
||
| Attachments: |
|
| Description |
|
MariaDB server is randomly crashing when ALTERing a table (adding a column), cannot always reproduce. Table is not useble after the crash and data is lost. Command used before the last crash: Attaching these files: |
| Comments |
| Comment by Elena Stepanova [ 2014-02-06 ] |
|
Hi, Thanks for reporting this. |
| Comment by azurit [ 2014-02-07 ] |
|
Unfortunately it's a production server BUT it was run on testing domain with testing database and there were no other access to the web at that time (so no other queries were running for 99%). |
| Comment by Elena Stepanova [ 2014-02-07 ] |
|
According to syslog that you provided, there were 16 open connections to the database server at the moment of the crash, so if it wasn't web access, maybe there were some maintenance works going on (backup, statistics, monitoring, anything). |
| Comment by azurit [ 2014-02-07 ] |
|
Yes, there were other cnnections and queries but to the other databases (i thought you were asking about that one database, not the whole server - you said 'related to the table'). |
| Comment by Elena Stepanova [ 2014-02-07 ] |
|
Yes, I meant those related to the table. I see, thank you. |
| Comment by azurit [ 2014-05-23 ] |
|
I had another crash with ALTER command, attaching logs. MariaDB version 5.5.37 (Debian Wheezy, 64bit). Command: ALTER TABLE `orders2` |
| Comment by Elena Stepanova [ 2014-06-01 ] |
|
Looks like a different one, but both are InnoDB assertion failures. Passing to Jan to his collection of InnoDB sporadic problems, maybe he'll be able to make sense out of it. |
| Comment by Jan Lindström (Inactive) [ 2014-07-04 ] |
|
Both crashed look like there is a corruption on InnoDB data dictionary that could be caused by HD failure. Can you still repeat this issue with more recent version of MariaDB ? |
| Comment by azurit [ 2014-07-04 ] |
|
The last crash was with 5.5.37, we are now running 5.5.38. Crashes are very rare and random so i can't tell if it's still reproducable. Crashes occured on different databases/tables (also on new, which were created after first few crashes) and we are using 'innodb_file_per_table = 1'. Also, server is running on RAID1 array and there is no single error logged in smart of all HDDs. |
| Comment by Jan Lindström (Inactive) [ 2014-07-04 ] |
|
I see. Is it possible to test with following change: revno: 4224 This is not a real fix, instead try to gather additional information |
| Comment by azurit [ 2014-07-04 ] |
|
Where am i supposed to download that patch? thnx |
| Comment by Jan Lindström (Inactive) [ 2014-07-04 ] |
|
bzr branch lp:maria/5.5 and build from sources at the moment |