Another 'MDL conflict db= table= ticket=10 solved by abort' issue

MySQL & MariaDB Percona XtraDB Cluster 8.x
1

Hi!

We encounter some issues with our new Percona MySQL 8 XtraDB cluster, in the logs we see these kind of messages:

2023-09-28T11:36:59.732634Z 24866 [Note] [MY-000000] [WSREP] MDL conflict db= table=2023-09-282023-09-28.done ticket=10 solved by abort
2023-09-28T11:36:59.732669Z 24866 [Note] [MY-000000] [WSREP] MDL conflict db= table=2023-09-282023-09-28.done ticket=10 solved by abort
2023-09-28T11:36:59.734753Z 24868 [Note] [MY-000000] [WSREP] MDL conflict db= table=2023-09-282023-09-28.done ticket=10 solved by abort

The issue looks the same as PXC-4148, only we’re running a newer version. Does anyone have the same problem? Or does anyone know what the problem could be?

Some information of our cluster:

  • Server version: 8.0.33-25.1 Percona XtraDB Cluster (GPL), Release rel25, Revision 0c56202, WSREP version 26.1.4.3
  • wsrep_OSU_method | TOI
  • wsrep_log_conflicts | ON
  • We’re using MaxScale and Corosync to ensure all read/write queries goes to one (and same) node
  • Ubuntu 22.04.3 LTS
  • 3 node setup
  • This is a new installation, we didn’t upgrade from MySQL 5.7 or something.

Thanks for your help!

2

Hi, please see the discussion in [PXC-4315] Regression of https://jira.percona.com/browse/PXC-4148 - Percona JIRA

3

Hello,
We also have this error, I submitted a report [PXC-4315] Regression of https://jira.percona.com/browse/PXC-4148 - Percona JIRA