[MDEV-18562] [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index Created: 2019-02-12  Updated: 2021-07-15  Resolved: 2019-10-30

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.2.16
Fix Version/s: 10.2.28, 10.3.19, 10.4.9

Type: Bug Priority: Major
Reporter: Marko Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 2
Labels: foreign-keys, galera, innodb
Environment:

Ubuntu 18.04

Attachments: Text File error.log     File mysql.tar.gz     File st_monitor_20190925_2208CEST.sql    
Issue Links:
Relates
relates to MDEV-26062 InnoDB: WSREP: referenced FK check fa... Closed

 Description   

Hello.

we are occasionally receiving error:

[ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `schema`.`child_table`;

What could be the cause for such error?
Is there any way to trace this issue?

Thanks for answer.

Regards,
Marko

 Comments   
Comment by George Diamantopoulos [ 2019-06-20 ]

I'm also getting this since yesterday, on 2 out of 3 galera nodes comprising of mariadb 10.3.14 instances.

What does this mean? Is it critical?

Comment by Sebastian Bergmann [ 2019-07-19 ]

We have the same behavior since upgrading to 10.3.16. Any news on this issue? Our application still seems to work properly.

2019-07-19  9:12:50 136990 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `FK_name` table `x`.`y`

Comment by Sebastian Bergmann [ 2019-09-16 ]

...? Logging Error ? Cluster will explode soon? Any comment please?

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

Hi, could you please share error log from node where this happens, its configuration and finally show create table for the table where lock wait happens.

Comment by Mark Ruys [ 2019-09-25 ]

Same error here, always the same table. It is a passive node in a Galera cluster.

Software:

  • Debian Buster
  • Galera 25.3.25-2
  • MariaDB 1:10.3.17-0+deb10u1
Comment by Jan Lindström (Inactive) [ 2019-10-29 ]

That message does not seem to be a fatal error, but I will enhance the message in case of normal lock wait case.

Comment by Lokendra patidar [ 2020-08-12 ]

any solution of this Error

Comment by Michal [ 2021-07-15 ]

Hi,

Using mariadb 10.5.10 ( this should be fixed in that version, per Git) and see these errors in log below.
Is it same issue ? Or is it another issue ? 

root@controller0:/home/ubuntu# cat /var/log/kolla/mariadb/mariadb.log  | grep refere
 
2021-07-13  9:09:17 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:10:02 841 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:10:13 836 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:10:37 841 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:13:29 813 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:13:37 854 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:16:45 845 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:25:41 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`portsecuritybindings`
 
2021-07-13  9:26:30 838 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:27:14 827 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:27:38 866 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:28:28 846 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:29:27 840 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13  9:43:39 842 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13 13:30:20 851 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-13 13:47:00 853 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`provisioningblocks`
 
2021-07-14 11:59:30 851 [ERROR] InnoDB: WSREP: referenced FK check fail: Lock wait index `PRIMARY` table `neutron`.`ml2_port_binding_levels`


(mariadb)[root@controller0 /]# dpkg -l | grep mari
 
ii  libmariadb3:amd64              1:10.5.10-2                    amd64        MariaDB database client library
 
ii  mariadb-backup                 1:10.5.10-2                    amd64        Backup tool for MariaDB server
 
ii  mariadb-client                 1:10.5.10-2                    all          MariaDB database client (metapackage depending on the latest version)
 
ii  mariadb-client-10.5            1:10.5.10-2                    amd64        MariaDB database client binaries
 
ii  mariadb-client-core-10.5       1:10.5.10-2                    amd64        MariaDB database core client binaries
 
ii  mariadb-common                 1:10.5.10-2                    all          MariaDB common configuration files
 
ii  mariadb-server                 1:10.5.10-2                    all          MariaDB database server (metapackage depending on the latest version)
 
ii  mariadb-server-10.5            1:10.5.10-2                    amd64        MariaDB database server binaries
 
ii  mariadb-server-core-10.5       1:10.5.10-2                    amd64        MariaDB database core server files

Logs above is from openstack wallaby version.

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