Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.1.22
-
PROD
Description
We have 3 nodes Galera cluster running MariaDB version 10.1.22-MariaDB. MariaDB crashes with
below error randomly on any node. Please help on the same.
2021-04-28 10:44:05 140327236836096 [Note] WSREP: cleanup transaction for LOCAL_STATE: set autocommit=1
|
terminate called after throwing an instance of 'std::out_of_range'
|
what(): vector::_M_range_check
|
210428 10:44:05 [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 https://mariadb.com/kb/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: 10.1.22-MariaDB
|
key_buffer_size=134217728
|
read_buffer_size=131072
|
max_used_connections=638
|
max_threads=1001
|
thread_count=602
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2325699 K bytes of memory
|
Hope that's ok; if not, decrease some variables in the equation.
|
|
Thread pointer: 0x0
|
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...
|