[MDEV-8656] MariaDB Galera Cluster crashed with Created: 2015-08-20  Updated: 2019-12-12  Resolved: 2019-12-12

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 5.5.45-galera
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: markus makela Assignee: Jan Lindström (Inactive)
Resolution: Won't Fix Votes: 0
Labels: galera
Environment:

CentOS 6.5


Attachments: File crash.tar.7z     File my.cnf    

 Description   

I ran into this crash while doing testing of donor nodes.

I was running a two node cluster while doing an insert of 3 million rows to one server. When this insert was ongoing to node 1, I killed the mysqld process on node 2 and started it up back again.

I repeated this process a few times and it seemed to work until it crashed. At the time of the crash the joining of the node took noticeably longer. After node 2 failed to start, I could not start again.

Attached are the configuration file and the contents of the /var/lib/mysql/ folder on the node which crashed.



 Comments   
Comment by Elena Stepanova [ 2015-08-21 ]

150820 21:49:13  InnoDB: Error: page 7 log sequence number 2631527373
InnoDB: is in the future! Current system log sequence number 1080772186.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.
...
 
InnoDB: Error: trying to access page number 7849 in space 0,
InnoDB: space name ./ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
150820 21:49:13  InnoDB: Assertion failure in thread 139932292278272 in file fil0fil.c line 5477
InnoDB: We intentionally generate a memory trap.

Comment by Jan Lindström (Inactive) [ 2019-12-12 ]

Support for 5.5-galera has ended.

Generated at Thu Feb 08 07:28:48 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.