Bug #95033 Failing assertion: btr_page_get_next(merge_page, mtr) == buf_block_get_page_no(b
Submitted: 16 Apr 2:41 Modified: 16 Apr 21:54
Reporter: 1993 robot Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server: Errors Severity:S2 (Serious)
Version:5.5.40 OS:CentOS
Assigned to: CPU Architecture:x86

[16 Apr 2:41] 1993 robot

In a cluster, mysql dies and cannot be automatically restored. I want to know what caused this crash and how to avoid it.

190215  3:43:07 InnoDB: The InnoDB memory heap is disabled
190215  3:43:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
190215  3:43:07 InnoDB: Compressed tables use zlib 1.2.7
190215  3:43:07 InnoDB: Using Linux native AIO
190215  3:43:07 InnoDB: Initializing buffer pool, size = 128.0M
190215  3:43:07 InnoDB: Completed initialization of buffer pool
190215  3:43:07 InnoDB: highest supported file format is Barracuda.
190215  3:43:07  InnoDB: Waiting for the background threads to start
190215  3:43:07  InnoDB: Assertion failure in thread 139873887680256 in file btr0btr.c line 3381
InnoDB: Failing assertion: btr_page_get_next(merge_page, mtr) == buf_block_get_page_no(block)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
190215  3:43:07 [ERROR] mysqld got signal 6 ;
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 http://kb.askmonty.org/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

Server version: 5.5.40-MariaDB-wsrep
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 9057682 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0x0 thread_stack 0x48000
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

How to repeat:
[16 Apr 9:55] zhai weixiang
Looks like your data is corruption. generally it's hard to verify without a repeatable case..
[16 Apr 9:56] zhai weixiang
You can innodb force recovery to start the instance and dump the data:
[16 Apr 13:52] Miguel Solorzano
Please check what was commented by zhai weixiang. Thanks.
[16 Apr 21:54] Bogdan Kecman

I'd say this is not MySQL Cluster ( https://www.mysql.com/products/cluster/ ) but maybe Innodb cluster or you are talking about simple replication setup that you call cluster. Please clarify what setup you are using.

> Server version: 5.5.40-MariaDB-wsrep

This is not MySQL server signature, please report a bug to MariaDB 

kind regards