wsrep commit callback does not release mdl locks

Bug #1245333 reported by Teemu Ollakka
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Status tracked in 5.6
5.5
Fix Released
High
Teemu Ollakka
5.6
Fix Released
High
Teemu Ollakka
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Status tracked in 5.6
5.5
Fix Released
Undecided
Unassigned
5.6
Fix Released
Undecided
Unassigned

Bug Description

Running statements

  create table foo (a int);
  insert into foo values (1);
  truncate foo;

on one node make slaves to log MDL conflicts

131028 7:01:23 [Note] WSREP: MDL conflict
request: (5 seqno 214 wsrep (1, 1, 0) cmd 0 8 truncate foo)
granted: (3 seqno 213 wsrep (1, 0, 0) cmd 0 133 (null))
131028 7:01:23 [Note] WSREP: MDL ticket: type: shared write space: TABLE db: test name: foo
131028 7:01:23 [Note] WSREP: MDL BF-BF conflict
request: (5 seqno 214 wsrep (1, 1, 0) cmd 0 8 truncate foo)
granted: (3 seqno 213 wsrep (1, 0, 0) cmd 0 133 (null))
131028 7:01:23 [Note] WSREP: MDL ticket: type: shared write space: TABLE db: test name: foo

This indicates that MDL locks are not released properly on slaves at commit time.

5.5 and 5.6 only.

Related branches

Revision history for this message
Teemu Ollakka (teemu-ollakka) wrote :
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1495

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.