random failures in flush_block_commit test
Bug #673988 reported by
Andrew Hutchings
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Drizzle |
Opinion
|
High
|
Andrew Hutchings | ||
| 7.0 |
Opinion
|
High
|
Andrew Hutchings | ||
Bug Description
main.flush_
drizzletest: At line 49: query 'reap' failed: 1205: Lock wait timeout exceeded; try restarting transaction
The result from queries just before the failure was:
drop table if exists t1;
create table t1 (a int) engine=innodb;
begin;
insert into t1 values(1);
flush tables with read lock;
select * from t1;
a
commit;
select * from t1;
a
unlock tables;
begin;
select * from t1 for update;
a
1
begin;
select * from t1 for update;
flush tables with read lock;
commit;
Related branches
lp:~linuxjedi/drizzle/trunk-bug-673998
- Drizzle Developers: Pending requested
-
Diff: 25 lines (+2/-2)2 files modifieddocs/options.rst (+1/-1)
tests/t/flush_block_commit.test (+1/-1)
| Changed in drizzle: | |
| importance: | Undecided → Critical |
| assignee: | nobody → Andrew Hutchings (linuxjedi) |
| milestone: | none → 2010-11-22 |
Revision history for this message
| Lee Bieber (kalebral-deactivatedaccount) wrote | #1 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #2 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #3 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #4 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #5 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #6 |
Revision history for this message
| Andrew Hutchings (linuxjedi) wrote | #7 |
To post a comment you must log in.
Andrew, we are seeing this again. we are only seeing this on our new OSX machines. The only difference I can see on these machines is that they are running boost 1.44, none of our other machines are running boost 1.44
-