WSREP: referenced FK check fail

Hello,

I am using percona xtradbcluster 8.0.25-15-1.focal. I am having below errors in my error logs randomly. Any advise how to fix it ?

2022-01-03T17:18:48.939875+05:00 385546 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.securitygroupportbindings
2022-01-14T18:11:30.801888+05:00 464605 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.provisioningblocks
2022-01-15T17:16:57.076709+05:00 471457 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.provisioningblocks
2022-01-15T17:39:59.800818+05:00 471473 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.securitygroupportbindings
2022-01-15T22:00:05.601212+05:00 473112 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.provisioningblocks
2022-01-16T14:19:21.180987+05:00 477360 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.securitygroupportbindings
2022-01-16T18:55:46.328378+05:00 478886 [ERROR] [MY-011825] [InnoDB] WSREP: referenced FK check fail: Lock wait index PRIMARY table neutron_ml2.securitygroupportbindings

Ammad

1 Like

@Ammad_Syed,
It looks like you have some FK violations. You need to run some SQL against the two tables and ensure that all FKs are properly matched. You can also drop the FK and recreate it as another check. If the FK can’t be created, that means you have missing data between the tables.

1 Like