[MDEV-13733] Server Crash - mysqld got exception 0xe06d7363 Created: 2017-09-04 Updated: 2020-12-08 Resolved: 2017-10-06 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Storage Engine - InnoDB |
| Affects Version/s: | 10.1.22 |
| Fix Version/s: | 10.1.24, 10.0.31, 10.2.7, 10.3.1 |
| Type: | Bug | Priority: | Major |
| Reporter: | Renaud | Assignee: | Unassigned |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | crash, innodb, lock | ||
| Environment: |
Windows 7 Professional - Service Pack 1 - 64 bits |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
We have a crash (happened 2 times in 4 days...) of MariaDB Server. Logs attached. Here's my ini file, don't hesitate if someone has remarks on it (even if not related to this bug) : my.ini [mysqld] max_allowed_packet=8M transaction-isolation=READ-COMMITTED slow_query_log=1 [client] thanks in advance for your help. |
| Comments |
| Comment by Renaud [ 2017-09-07 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
We had again the crash this night, please help...
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2017-09-07 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
As our InnoDB expert marko has found out, it is most likely a duplicate of MySQL bug which was fixed here:
This bugfix should be in versions 10.0.31, 10.1.24, 10.2.7, 10.3.1. You have 10.1.22, so please try to upgrade to the latest 10.1 and see if it helps. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Renaud [ 2017-09-07 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks Elena, we have done a lot of tests (regression, performance, etc...) with version 10.1.22, so i was wondering if there's a risk to upgrade from 10.1.22 to 10.1.26 ? thanks for your help. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Elena Stepanova [ 2017-09-07 ] | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
For defaults, there was one change between these versions, the default value of innodb_empty_free_list_algorithm has changed from BACKOFF to LEGACY. If you are using some dynamic plugins/engines, there could have been changes as well. Naturally, any upgrade involves risks – even if there are no known regressions between versions, there certainly can be hidden ones, maybe something very specific to your particular workflow. However, sooner or later you will have to upgrade – if not on any other reason, then because of security fixes, there have been quite a few already since 10.1.22, and they will keep coming. Given that and the crashes that you encounter, you could just as well start evaluating the new version now. |