Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

After upgrade to 8.0.30 errors: MDL conflict db= table= ticket=10 solved by abort

Description

Multiple users are reporting this error after upgrading to 8.0.30

This error tends to appear on a single node situation, when the first node is bootstraped into the cluster and upgraded.

Link to the original post:

[After upgrade to 8.0.30 errors: MDL conflict db= table= ticket=10 solved by abort|https://forums.percona.com/t/after-upgrade-to-8-0-30-errors-mdl-conflict-db-table-ticket-10-solved-by-abort/19653]

Environment

None

Activity

Show:

Alaa Alhallah April 6, 2023 at 2:02 PM

Hi @Zsolt Parragi
I updated my cluster as you recommanded to version 8.0.31-23.1

but today I got the same problem and my cluster is crashed

saikumar.vs February 22, 2023 at 1:48 PM
Edited

HI, i have update my previous comments, indeed i somehow copied the wrong set of errors.

Also i dont see any errors with Percona-XtraDB-Cluster_8.0.29-21.1, at all related to MDL conflict, but only Percona-XtraDB-Cluster_8.0.30-22.1.

yunus.uyanik February 22, 2023 at 7:29 AM

Exactly, just started 8.0.30 and then mysqlslap.

Kamil Holubicki February 21, 2023 at 2:52 PM

,

That's great! So no upgrade from 5.7 needed? Just start 8.0.30 and then mysqlslap?

yunus.uyanik February 21, 2023 at 2:19 PM
Edited

I can reproduce that with this scenario.

The logs will appear like below

 

Done

Details

Assignee

Reporter

Fix versions

Affects versions

Priority

Smart Checklist

Created February 9, 2023 at 12:40 PM
Updated March 6, 2024 at 8:45 PM
Resolved February 22, 2023 at 1:19 PM