Details
-
Bug
-
Status: Closed (View Workflow)
-
Critical
-
Resolution: Duplicate
-
10.1.28
-
None
Description
User is encountering MariaDB 10.1.28 crashing on binlog switch to new file.
180209 13:45:23 [ERROR] mysqld got signal 11 ;
|
This could be because you hit a bug. It is also possible that this binary
|
or one of the libraries it was linked against is corrupt, improperly built,
|
or misconfigured. This error can also be caused by malfunctioning hardware.
|
|
|
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
|
|
|
We will try our best to scrape up some info that will hopefully help
|
|
|
Server version: 10.1.28-MariaDB
|
key_buffer_size=16777216
|
read_buffer_size=262144
|
max_used_connections=56
|
max_threads=1002
|
thread_count=58
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 806565 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
Query:
Query (0x7fa111acc020): delete from task where starttimeutc <'2017-09-01 12:12:44' LIMIT 100000
|
They are trying to delete 100000 rows from a table with approx 10710898 rows.
Their max_binlog_size = 2M, which has been recommended to them to increase. But still, there should not be a crash.
Note that the stack traces look very similar to these:
https://jira.mariadb.org/browse/MDEV-14290
https://jira.mariadb.org/browse/MDEV-14314
However, the above both mention RocksDB, which this user is not using. However, Andrii stated in the latter report that, "According to MDEV-14290 and my tests the crash happens on any binlog rotation, so I will mark this as duplicate", so perhaps it is not limited to RocksDB. If it could be related, the fix in 14290 was only applied to 10.2 though, per the bug report.
Attachments
Issue Links
- duplicates
-
-
- Closed
-