Bug #38070 rpl_locktrans_innodb Lock wait timeout exceeded At line 632
Submitted: 12 Jul 2008 14:26 Modified: 7 May 2009 12:45
Reporter: Andrei Elkin Email Updates:
Status: Closed Impact on me:
None 
Category:Tests: Replication Severity:S3 (Non-critical)
Version:6.0 OS:Any
Assigned to: Ingo Strüwing CPU Architecture:Any
Tags: pushbuild, rpl_locktrans_innodb, sporadic, test failure

[12 Jul 2008 14:26] Andrei Elkin
Description:
Failed having:

        tfl_name: rpl.rpl_locktrans_innodb 'stmt'
    tfl_tst_type: ps_stm
        psh_tree: bzr_mysql-6.0-bugteam
       psh_order: 35
tfl_bld_platform: powermacg5
        tfl_text: rpl.rpl_locktrans_innodb 'stmt' [ fail ]

mysqltest: In included file "./include/locktrans.inc": At line 632: query 'reap' failed: 1205: Lock wait timeout exceeded; try restarting transaction

How to repeat:
https://intranet.mysql.com/secure/pushbuild/xref.pl?startdate=&enddate=&dir=&plat=&testtyp...
[12 Jul 2008 14:27] Andrei Elkin
Bug #29828 failed at the same line. Leaving this bug as the parent because more details reported here.
[14 Jul 2008 6:01] Alexander Nozdrin
See also Bug#37712.
[29 Jul 2008 22:25] Omer Barnir
triage: setting tag to sr60test
[15 Sep 2008 9:43] Bugs System
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/54066

2697 Serge Kozlov	2008-09-15
      Bug#38070. Set innodb_lock_wait_timeout to 5 instead 1 because 
      lock wait timeout exceeded too often.
[2 Feb 2009 8:33] Ingo Strüwing
The bug was reassigned to me in "in progress" state. It doesn't have sufficient priority to handle it at the moment. Set back to "verified" for now (though it has not been verified yet).
[2 Feb 2009 12:16] Ingo Strüwing
Oops, I didn't mean to un-assign it from me.
[6 Mar 2009 11:58] Bugs System
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/68486

2790 Ingo Struewing	2009-03-06
      Bug#38070 - rpl_locktrans_innodb Lock wait timeout exceeded At line 632
      
      The test case rpl_locktrans_innodb failed sporadically.
      A lock wait timed out on slow machines.
      
      Instead of just increasing the timeouts, two tests do now allow timeouts
      to happen. This does not invalidate the purpose of the tests. Please find
      detailed explanation in the test script.
     @ mysql-test/include/locktrans.inc
        Bug#38070 - rpl_locktrans_innodb Lock wait timeout exceeded At line 632
        Changed two tests to allow for lock wait timeout.
     @ mysql-test/r/locktrans_innodb.result
        Bug#38070 - rpl_locktrans_innodb Lock wait timeout exceeded At line 632
        Updated test result.
     @ mysql-test/suite/rpl/r/rpl_locktrans_innodb.result
        Bug#38070 - rpl_locktrans_innodb Lock wait timeout exceeded At line 632
        Updated test result.
[23 Mar 2009 15:46] Ingo Strüwing
Both reviewers checked their box: -> approved.
[23 Mar 2009 16:48] Ingo Strüwing
Queued to mysql-6.0-backup.
[23 Apr 2009 7:19] Bugs System
Pushed into 6.0.11-alpha (revid:alik@sun.com-20090423070920-e5lq3vrrqi016z2c) (version source revid:alik@sun.com-20090423070920-e5lq3vrrqi016z2c) (merge vers: 6.0.11-alpha) (pib:6)
[7 May 2009 12:45] Jon Stephens
Tests only, no user changes to document. Closed.