MySQL Bugs: #18352: Rollback + NF can lead to stray locks

Bug #18352	Rollback + NF can lead to stray locks
Submitted:	20 Mar 2006 13:06	Modified:	27 Mar 2006 15:43
Reporter:	Jonas Oreland
Status:	Closed
Category:	Server: Cluster	Severity:	S1 (Critical)
Version:	4.1,5.0,5.1	OS:
Assigned to:	Jonas Oreland	Target Version:

Description:
Rollback + NF can lead to stray locks
This can also "easily" be accomplished by using high value for TransactionDeadLock
timeout
  (>6 minutes)

How to repeat:
begin;
update t1 set b = 12 where a = 13;

-- restart node which holds primary copy, and not being TC.
rollback;

A stray lock on backup node will occur.
This lock is impossible to remove wo/ restarting node.

https://intranet.mysql.com/secure/mailarchive/mail.php?folder=5&mail=49474

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3975

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3976

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

  http://lists.mysql.com/commits/3977

...running autotest with old/new code

pushed into 5.1.8

pushed into 5.0.20

pushed into 4.1.19

Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Documented bugfix in 4.1.19, 5.0.20, 5.1.8 changelogs. Closed.