[MDEV-15307] MariaDB 10.1 crashing on binlog switch to new file Created: 2018-02-13  Updated: 2020-08-25  Resolved: 2018-02-14

Status: Closed
Project: MariaDB Server
Component/s: Galera, Replication
Affects Version/s: 10.1.28
Fix Version/s: 10.1.30

Type: Bug Priority: Critical
Reporter: Chris Calender (Inactive) Assignee: Andrei Elkin
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-9510 Segmentation fault in binlog thread c... Closed

 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.



 Comments   
Comment by Elena Stepanova [ 2018-02-13 ]

Crash in MYSQL_BIN_LOG::mark_xid_done points at MDEV-9510 and related bugs (it's a big cluster of bugs), but I don't remember ever seeing MYSQL_BIN_LOG::unlog, so assigning to Elkin to check.

Comment by Andrei Elkin [ 2018-02-14 ]

This one must be a duplicate of MDEV-9510 fixed in 10.1.30.

Generated at Thu Feb 08 08:20:16 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.