Not the answer you need?
Register and ask your own question!

Cluster down > BF-BF X lock conflict

pathetpathet ContributorInactive User Role Beginner

today we had a strange problem with our PXC (5.5.41-25.12-855.trusty
). All 3 nodes were offline.

I found something in the error logs:
BF-BF X lock conflict

RECORD LOCKS space id 1965277 page no 68 n bits 120 index `PRIMARY` of table `data_mdt`.`V30_55_044` trx id A72E0B521 lock_mode X locks rec but not gap

07:13:22 UTC - 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.

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.

Please help us make Percona XtraDB Cluster better by reporting any

bugs at







It is possible that mysqld could use up to

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343066 K bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f2f9c000990

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 = 7f3d08332a58 thread_stack 0x40000





























Trying to get some variables.

Some pointers may be invalid and cause the dump to abort.

Query (0): is an invalid pointer

Connection ID (thread ID): 14
You may download the Percona XtraDB Cluster operations manual by visiting You may find information

in the manual which will help you identify the cause of the crash.

170911 09:13:22 mysqld_safe Number of processes running now: 0

170911 09:13:22 mysqld_safe WSREP: not restarting wsrep node automatically

170911 09:13:22 mysqld_safe mysqld from pid file /var/lib/mysql/ ended

Two questions:

- Why stopped our PXC ?
- I think the error was at 07:13:22 am, put why stopped the nodes at 09:13:22 ?

Any ideas ? :-/

best regards
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.