[MDEV-16793] DDL shouldn't have completed in part of the nodes if one of them was unable to enter TOI Created: 2018-07-20  Updated: 2018-09-02  Resolved: 2018-09-02

Status: Closed
Project: MariaDB Server
Component/s: Galera
Affects Version/s: 10.1.22
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Fernando L Camargos Assignee: Jan Lindström (Inactive)
Resolution: Cannot Reproduce Votes: 0
Labels: None

Attachments: File isp-210853076-1-343206816_0607err.log.short.edited-e     File isp-210853077-1-343206891_0607err.log.short.edited-e     File isp-210853078-1-343206966_0607err.log.short.edited-e    

 Description   

On the attached logs we see a DDL event succeeding in two of the nodes but failing in the third one at 2:31:57:

2018-06-07  2:31:57 140668603120384 [Note] WSREP: abort transaction: BF: /* ApplicationName=DBeaver 2.4.1 - Main connection */ *alter table delivery add column lock_count integer* victim: (null)
 
2018-06-07  2:31:57 140668603120384 [Note] WSREP: cluster conflict due to high priority abort for threads:

The DDL was retried at 3:44:47 and failed again, finally succeeding at 13:07:58:

2018-06-07 13:07:58 140186596428544 [Note] WSREP: TO BEGIN: -1, 0 : alter table appt_scheduler_PROD.delivery add column lock_count integer
 
2018-06-07 13:07:58 140186596428544 [Note] WSREP: TO BEGIN: 27163806, 2
 
2018-06-07 13:07:58 140186596428544 [Note] InnoDB: Online DDL : Start
 
(...)
 
2018-06-07 13:08:00 140186596428544 [Note] InnoDB: *Online DDL : Completed*
 
2018-06-07 13:08:00 140186596428544 [Note] WSREP: avoiding binlog rotate due to TO isolation: 1

It should not have completed on the other two nodes if one of the nodes was unable to enter Total Order Isolation.

 Comments   
Comment by Jan Lindström (Inactive) [ 2018-09-02 ]

I strongly suggest upgrading your server to more recent version and if issue is repeatable there please provide again full error logs from all galera nodes preferable using wsrep-debug=ON configuration. BF (brute force) aborts are not yet sign of a bug, they can happen.

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