| Showing 1-100 of 2733 (Edit, Save, CSV, Feed) | Show Next 100 Entries » |
| ID# | Date | Type | Status | Sev | Version | Target | OS | Summary | Assigned |
|---|---|---|---|---|---|---|---|---|---|
| 38085 | 2008-07-13 15:38 | Server: Cluster | No Feedback (1170 days) | S3 | Any | rpl_ndb.rpl_ndb_basic: 'Lock wait timeout exceeded...' At line 8 | |||
| 15005 | 2005-11-17 6:28 | Server: Cluster | Duplicate (2368 days) | S3 | 5.0.15 | Miracle Linux V3.0 | MySQL Cluster respond "Lock wait timeout exceeded" after issuing SELECT stateme | ||
| 12222 | 2005-07-27 18:17 | Server: Cluster | Closed (2436 days) | S2 | 5.1-wl2325 | Linux (Linux) | One instance of TPC-B is getting Lock wait timeout exceeded (new cluster drop) | Pekka Nousiainen | |
| 51544 | 2010-02-26 9:39 | Server: Cluster | Can't repeat (569 days) | S3 | 7.0.* | Any | select (no locking) fails with "lock wait timeout exceeded" | Jonas Oreland | |
| 40044 | 2008-10-15 12:27 | Server: Maria | Closed (1233 days) | S3 | 5.1-maria | Microsoft Windows | Maria: maria.test fails under Windows (lock wait timeout) | Sergei Golubchik | |
| 38070 | 2008-07-12 14:26 | Tests: Replication | Closed (1114 days) | S3 | 6.0 | 6.0 | Any | rpl_locktrans_innodb Lock wait timeout exceeded At line 632 | Ingo Struewing |
| 56422 | 2010-08-31 19:28 | Server | Closed (552 days) | S3 | 5.5.6-m3, 5.6.0-m4, 5.6.99 | 5.5+ | Any | CHECK TABLE run when the table is locked reports corruption along with timeout | Jon Olav Hauglid |
| 5785 | 2004-09-28 12:36 | Server: Cluster | Closed (2796 days) | S2 | mysql 4.1.6 | Fermi Linux LTS 3.01 | lock timeout during concurrent update | Tomas Ulin | |
| 28685 | 2007-05-25 19:11 | Server: Tests | Can't repeat (1184 days) | S3 | 5.1.19 | 5.1+ | Any | Suite "rowlock" fails totally: "Lock wait timeout exceeded", common include file | |
| 27380 | 2007-03-22 17:25 | Server | Not a Bug (1887 days) | S2 | 5.0.22 and 5.0.37 | Linux (RedHat Enterprise 4) | Problems Deleting Data from InnoDB | ||
| 38087 | 2008-07-13 16:01 | Server: Cluster | No Feedback (1170 days) | S3 | Any | rpl_truncate_7ndb failed at At line 15: replace into mysql.ndb_apply_status | |||
| 22106 | 2006-09-08 6:46 | Server: DML | Verified (1633 days) | S3 | 5.0.26-BK | Linux (Linux) | can't output to error log file when INNODB happened ERROR1205 | ||
| 57167 | 2010-10-01 13:08 | Server: Locking | Won't fix (399 days) | S3 | mysql-next-mr-wl3561 | Any | Misleading error for LOCK TABLE t1 IN SHARE MODE NOWAIT | ||
| 4852 | 2004-08-02 7:04 | Server: InnoDB | Can't repeat (1334 days) | S3 | 4.0.21-nightly-20040729-Max-log | Linux (Linux RHEL AS 3.0) | lock tables ... write still works wrong | Marko Mäkelä | |
| 41521 | 2008-12-16 21:05 | Server: Falcon | Closed (1114 days) | S3 | mysql-6.0-falcon | 6.0.10 | Any | falcon_bug_34174 fails with lock wait timeout, sometimes | Hakan Küçükyılmaz |
| 20725 | 2006-06-27 14:05 | Server: Cluster | Closed (2157 days) | S3 | 5.1.12 | Linux (Linux 32 bit OS) | MySQLD cluster use "fast count" is broken | Stewart Smith | |
| 48939 | 2009-11-20 11:30 | Server: General | Duplicate (907 days) | S2 | mysql-next | Any | First character in error text replaced with Z on DBUG_EXTRA builds | Mattias Jonsson | |
| 41667 | 2008-12-22 1:54 | Server: Locking | Not a Bug (1250 days) | S3 | 5.0.67 | Microsoft Windows (XP SP3) | Lock wait timeout exceeded when updating a row in a reference table | ||
| 8324 | 2005-02-04 18:38 | Server: Cluster | Can't repeat (2657 days) | S3 | 4.1.9-max-log | HP/UX (HP-UX B.11.23 U ia64) | AUTOCOMMIT=ON causes Lock wait timeout with small Cluster table | Martin Skold | |
| 65130 | 2012-04-27 12:12 | Server: Cluster | Verified (14 days) | S3 | 7.1.x, 7.2.5 | Linux | "Transaction already aborted" hides real error msg on INSERT ... ON DUP UPDATE | ||
| 33819 | 2008-01-11 13:00 | Server: Cluster | Verified | S3 | mysql-5.0 | CGE | Linux | single PK-only query transactiosn fail with deadlock timeout on BLOB tables | Takeover System Account |
| 52832 | 2010-04-14 18:46 | Server: Cluster | No Feedback (658 days) | S1 | 5.1.35-ndb-7.0.7 | Linux (CentOS 5.3) | Random lock up - Lock wait timeout exceeded - NDBCluster | ||
| 40515 | 2008-11-05 0:18 | Server: Partition | Closed (1221 days) | S3 | 5.1.26,5.1.29 | 5.1+ | Any | Query on a partitioned table does not return 'lock wait timeout exceeded' | Mattias Jonsson |
| 65153 | 2012-04-30 6:26 | Server: Locking | Need Feedback (25 days) | S2 | 5.1.45 | Linux (Fedora) | InnoDB locking issues after mysql crash recovery | ||
| 37775 | 2008-07-01 15:46 | Tests: Server | Verified (1053 days) | S3 | 6.0-BK,5.4 | 5.5+ | Any | main.locktrans_innodb and rpl.rpl_locktrans_innodb fail randomly | |
| 59969 | 2011-02-05 21:41 | Tests: Cluster | Verified | S3 | 7.1.10 | Any | Test 'ndb_blob_big' times out in locking | ||
| 36859 | 2008-05-21 20:08 | Server: Errors | Verified (1331 days) | S3 | 5.1.24-rc | Any | The optimize api does not handle the HA_ERR_LOCK_WAIT_TIMEOUT error. | ||
| 9045 | 2005-03-08 10:09 | Server: Cluster | To be fixed later (2635 days) | S3 | Any | Lock wait timeout when using table with TEXT column | Jonas Oreland | ||
| 51966 | 2010-03-11 19:08 | Server: Locking | No Feedback (772 days) | S3 | 5.1.40-community | Any | INSERT ... SELECT should allow concurrent inserts when binary log is disabled. | ||
| 39705 | 2008-09-28 4:24 | Tests | Duplicate (379 days) | S3 | 6.0, 6.0-falcon, 5.1 | Any | read_many_rows_innodb fails | ||
| 41564 | 2008-12-17 18:35 | Server: Falcon | Duplicate (1253 days) | S3 | 6.0.9 | 6.0.10 | Any | Falcon; incorrect lock wait timeouts can occur | Kevin Lewis |
| 44581 | 2009-04-30 16:44 | Server: Replication | Closed (1051 days) | S2 | 5.1.34 and 5.4.0 | 5.1.37 | Any | Slave stops when transaction with non-transactional table gets lock wait timeout | Alfranio Correia |
| 29828 | 2007-07-16 15:28 | Server: Replication | Duplicate (1413 days) | S3 | 5.2.4-alpha | HP/UX (11.11 32 bit) | Test 'rpl_locktrans_innodb' failed on HP-UX 11.11 32 bit | Sveta Smirnova | |
| 29490 | 2007-07-02 15:42 | Server: Cluster | No Feedback (1223 days) | S1 | 5.0.44 | CGE | Linux | Lock wait timeout error in NDB during concurrent SELECTs | Jonas Oreland |
| 47180 | 2009-09-07 18:17 | Server: Locking | No Feedback (947 days) | S1 | 5.0.27 | Linux | ERROR 1205 (HY000): Lock wait timeout exceeded; try restarting transaction. | ||
| 41500 | 2008-12-16 13:05 | Tests: Cluster | Verified | S2 | 5.1, 6.0 | Any | ndb_basic fails sporadically with "lock wait timeout exceeded" | ||
| 3894 | 2004-05-26 5:52 | Server: InnoDB | Closed (2916 days) | S2 | 4.0.20 | Linux (RedHat Linux) | lock tables ... write works wrong | Marko Mäkelä | |
| 46664 | 2009-08-12 3:10 | Server: Locking | Closed (955 days) | S3 | 5.4.4-alpha | 5.4+ | Any | NOWAIT in SHARE mode causes immediate timeout although the table is not locked | Magne Mæhre |
| 13079 | 2005-09-09 1:18 | Server | Can't repeat (2431 days) | S2 | 4.1.13 | Linux (Linux 2.6.12) | NDB/cluster reports excessive wait lock timeouts on table operations | ||
| 43734 | 2009-03-18 20:53 | Server: Locking | Can't repeat (927 days) | S2 | 5.1.30 | Microsoft Windows (XP Pro SP2) | SELECT ... ORDER BY ... FOR UPDATE lock may be broken | ||
| 11015 | 2005-06-01 12:03 | Server: Cluster | No Feedback (2518 days) | S1 | 4.1.11 | Linux (Linux) | massive concurrent inserts cause error or server crash | ||
| 55911 | 2010-08-11 13:01 | Server: Cluster | Verified (652 days) | S2 | mysql-5.1-telco-7.0 | Linux (Red Hat 3.4.6-8) | Error updating primary key on more than one entry | ||
| 39392 | 2008-09-11 12:58 | Server: Maria | Closed (1320 days) | S3 | 5.1-maria | 6.0-beta | Linux | Maria: if INSERT in UNIQUE finds uncommitted same key, error instead of wait | Sergei Golubchik |
| 19201 | 2006-04-19 17:08 | Server: Cluster | Closed (2204 days) | S2 | 4.1 -> | Linux (Linux) | TRUNCATE table with blobs fails with 1205 | Pekka Nousiainen | |
| 23456 | 2006-10-19 8:39 | Server | Not a Bug (2045 days) | S2 | cluster 5.0.22 | Sun Solaris (solaris 9) | ODBC Error (S1T00,4B5) | ||
| 28622 | 2007-05-23 15:03 | Server: Cluster | Can't repeat (756 days) | S3 | mysql-5.0 | CGE | Linux | REPLACE INTO cause DELETE to time out on lock | Martin Skold |
| 51204 | 2010-02-16 6:13 | Server: General | No Feedback (801 days) | S5 | Linux (ubantu) | Lock wait timeout exceeded; try restarting transaction | |||
| 46151 | 2009-07-13 15:12 | Server: Falcon | Unsupported (730 days) | S3 | 6.0.12-bzr | Sun Solaris | falcon_bug_34174 fails with lock wait timeout when pool-of-threads is enabled | Olav Sandstaa | |
| 9265 | 2005-03-18 6:37 | Server | Not a Bug (2519 days) | S1 | 14.1.14 | Linux (linux) | mysql cluster "Lock" | ||
| 40737 | 2008-11-14 12:14 | Server: Locking | Not a Bug (1017 days) | S2 | 5.0.67 | Any | Lock wait timeout exceeded during inserting row | ||
| 50723 | 2010-01-29 10:01 | Server: InnoDB | Closed (10 days) | S1 | 5.0, 5.1 | Any | InnoDB CHECK TABLE fatal semaphore wait timeout possibly too short for big table | Marko Mäkelä | |
| 37994 | 2008-07-09 14:46 | Server: InnoDB | No Feedback (1217 days) | S2 | 5.0.51a-community | Any (seen on windows server 2003 and linux) | InnoDb waits for lock when DELETE from a table previously in a interrupted trans | ||
| 8825 | 2005-02-26 22:39 | Server: InnoDB | Won't fix (2644 days) | S2 | 4.0.22 | Linux (Linux) | Fail to remove foreign key constraint | Jani Tolonen | |
| 54767 | 2010-06-24 10:35 | Server: Docs | Closed (700 days) | S3 | 5.5.4-m3 | Any | Please document the effect of metadata locks taken by failing statements | Paul DuBois | |
| 9341 | 2005-03-22 16:29 | Server: Cluster | No Feedback (2570 days) | S2 | 4.1.9 | Linux (Redhat) | do not lock tables for reading | Jonas Oreland | |
| 28004 | 2007-04-21 19:42 | Server: InnoDB | Closed (1859 days) | S3 | 5.0.27 | Microsoft Windows | Using transaction in C# lock time out problem | Heikki Tuuri | |
| 57481 | 2010-10-15 12:22 | Server: Cluster | Closed (547 days) | S3 | 5.1.47-ndb-7.1.9 | Any | 'multi range read' may fail to close completed NdbScanOperations | Ole John Aske | |
| 49620 | 2009-12-11 12:21 | Server: Replication | Can't repeat (886 days) | S3 | 5.1.43, 5.1, next-mr bzr | Any | Repl diff with concurrent transactions with trigger+savepoint+lock wait timeout | Alfranio Correia | |
| 43554 | 2009-03-11 9:16 | Server: Falcon | Unsupported (730 days) | S3 | 6.0-falcon-team | Any | Intermittent lock-wait-timeout in falcon_deadlock test | Kevin Lewis | |
| 29452 | 2007-06-29 21:13 | Server: Falcon | Closed (1635 days) | S3 | 6.0.1-alpha-debug | Linux (SUSE 10 64-bit) | Falcon: two-way deadlock with unique index and trigger | Kevin Lewis | |
| 51920 | 2010-03-10 16:14 | Server: InnoDB | Closed (695 days) | S3 | 5.0.84, 5.1.45, 5.5 | 5.1+ | Any | Innodb connections in row lock wait ignore KILL until lock wait timeout | John Russell |
| 63730 | 2011-12-13 9:53 | Server: Locking | Duplicate (158 days) | S3 | mysql-5.1.56 ndb-7.1.15 | Sun Solaris (sol10) | Update different rows of table in Function will cause 'Lock Wait Timeout' | ||
| 18808 | 2006-04-05 14:25 | Server: Cluster | Duplicate (2226 days) | S3 | 5.1.9 | Linux (Linux 32 Bit OS) | "Rowid already allocated" Error duing update and not during node recovery | Jonas Oreland | |
| 24144 | 2006-11-09 14:20 | Server: Locking | Duplicate (1437 days) | S2 | 5.1-BK | Linux (Linux) | strange transactional behaviour: DROP TABLE drops also locks | Dmitry Lenev | |
| 45066 | 2009-05-25 12:21 | Server: Locking | Closed (810 days) | S3 | 5.1 | Any | FLUSH TABLES WITH READ LOCK deadlocks against LOCK TABLE | Jon Olav Hauglid | |
| 25913 | 2007-01-29 12:40 | Server: Cluster | Duplicate (1842 days) | S2 | 5.1.16-beta | Linux (SuSE 11, x64) | rpl_ndb_dd_advance fails randomly | Takeover System Account | |
| 38088 | 2008-07-13 16:03 | Server: Cluster | No Feedback (1170 days) | S3 | 6.0 | Any | rpl_row_basic_7ndb failed At line 55 INSERT INTO t2 ... | ||
| 38660 | 2008-08-08 8:50 | Server: Replication | No Feedback (1261 days) | S2 | 5.0.51a, 5.1.26 | Linux | Lock wait timeout exceeded while failing-over on master-master replication setup | ||
| 29386 | 2007-06-27 12:42 | Server: Cluster | No Feedback (1547 days) | S3 | 5.1.16 | Linux (Cluster failure on contineous insertion) | Cluster failure on contineous insertion | ||
| 11966 | 2005-07-15 12:01 | Server | Not a Bug (2448 days) | S3 | HP/UX (HP-UX 11.i) | MySQL throws native error code : 1205 , | |||
| 34990 | 2008-03-03 1:41 | Server: Falcon | Closed (1328 days) | S2 | 6.0.4 | 6.0.5 | Any | Falcon: falcon_bug_34351_A & falcon_bug_34251_C fail periodically | Kevin Lewis |
| 42209 | 2009-01-20 8:30 | Server: Optimizer | Verified | S3 | 5.1.30 | Any | Rollback affects the index usage for DELETE statement with FORCE INDEX. | ||
| 11360 | 2005-06-15 19:57 | Connector/J | No Feedback (2504 days) | S3 | 3.1.8 | Microsoft Windows (Windows XP) | Connector/J dumping query into SQLException twice | ||
| 48106 | 2009-10-16 7:50 | Server: InnoDB | No Feedback (921 days) | S3 | 5.0.67 | Any | Concurrent DELETE / INSERT throw lock wait timeout | ||
| 33474 | 2007-12-21 23:02 | Server: Falcon | Closed (1484 days) | S3 | 6.0 | Any | falcon_lock_timeout is different from innodb_wait_lock_timeout | Kevin Lewis | |
| 44783 | 2009-05-11 12:00 | Server: Falcon | Duplicate (1044 days) | S3 | falcon-team | 6.0+ | Any | A SELECT using ORDER BY and LIMIT sometimes returns too many rows | Takeover System Account |
| 12081 | 2005-07-21 13:17 | Server: Cluster | Can't repeat (2432 days) | S3 | 4.1.12 | Linux (Linux/x86) | Cluster: BEGIN after lock-wait timeout results in error 1296 | Martin Skold | |
| 49348 | 2009-12-02 13:10 | Server: Backup | Won't fix (896 days) | S2 | 6.0-backup | Any | backup_wait_timeout behaves differently from the other timeouts | Ritheesh Vedire | |
| 43630 | 2009-03-13 11:31 | Server: Falcon | Closed (946 days) | S2 | falcon-team | Any | A SELECT using ORDER BY and LIMIT sometimes returns no rows | Lars-Erik Bjørk | |
| 37716 | 2008-06-28 11:20 | Tests: Replication | Closed (1114 days) | S2 | 6.0, 5.1 | 5.1+ | Any | rpl.rpl_deadlock_innodb 'row' failed on pushbuild | Serge Kozlov |
| 45086 | 2009-05-26 7:10 | Server: Falcon | Duplicate (1044 days) | S3 | 6.0.11 | 6.0+ | Any | A SELECT using ORDER BY and LIMIT sometimes misses one row | Takeover System Account |
| 42474 | 2009-01-30 12:40 | Server: Cluster | Duplicate (1193 days) | S1 | 6.4.2 | Sun Solaris | Requests blocked in MySQL Cluster | Takeover System Account | |
| 2896 | 2004-02-19 14:25 | MySQL Administrator | Closed (3017 days) | S3 | 1.0.1a ALPHA | Any (All) | Value name for Wait Timeout is 'wait_amount' instead of 'wait_timeout' | Ulrich Bayer | |
| 42903 | 2009-02-16 20:11 | Server: Falcon | Unsupported (730 days) | S1 | 6.0-falcon-team | Any | Falcon: Inconsistent tablespace after recovery | Lars-Erik Bjørk | |
| 47020 | 2009-08-31 14:35 | Server: Cluster | Duplicate (996 days) | S1 | 7.0.5 | Linux | MySQL Cluster 7.0.5 datas nodes crash | Jonas Oreland | |
| 47343 | 2009-09-16 1:23 | Server: Partition | Closed (705 days) | S1 | 5.1.38 | 5.1.44+ | Any | InnoDB fails to clean-up after lock wait timeout on REORGANIZE PARTITION | Mattias Jonsson |
| 56601 | 2010-09-06 19:06 | Tests: Engine | Closed (556 days) | S3 | 5.5.6-m3 | 5.5+ | Microsoft Windows | Test uses Unix path for temporary file, fails, and writes misleading message | Mattias Jonsson |
| 3153 | 2004-03-12 4:58 | Server: InnoDB | Can't repeat (2987 days) | S2 | 4.0.16 | HP/UX (HPUX11.11) | bad result set data with "SELECT...FOR UPDATE" | Dean Ellis | |
| 18856 | 2006-04-06 17:05 | Server: Cluster | Closed (1739 days) | S2 | 5.1 | 5.1.22 | Linux (Linux) | Table remains locked after SELECT * INTO OUTFILE statment. | Jonathan Miller |
| 54905 | 2010-06-30 0:07 | Server: Locking | Closed (652 days) | S3 | 5.5.5-m3 | 5.5+ | Any | Connection with WRITE lock cannot ALTER table due to concurrent SHOW CREATE | Jon Olav Hauglid |
| 37346 | 2008-06-11 14:35 | Server: Locking | Closed (810 days) | S3 | 5.0,5.1 | 5.5+ | Any | innodb does not detect deadlock between update and alter table | Dmitry Lenev |
| 21105 | 2006-07-18 7:16 | Server | No Feedback (2053 days) | S3 | 5.0.21 | Linux (SLES 9 PPC) | Connections are not kill by server after timeout | ||
| 39498 | 2008-09-17 13:49 | Server: Cluster | Verified | S2 | mysql-5.1-telco-6.3 | Any | Doing INSERT INTO .. SELECT brings down all data nodes. | ||
| 40746 | 2008-11-14 15:03 | Server: InnoDB | Not a Bug (1288 days) | S2 | 5.0.67 | Microsoft Windows (XP SP2) | SQL locks more rows that we asked to lock | ||
| 28899 | 2007-06-05 14:55 | Server: Cluster | Closed (1810 days) | S3 | Any | not possible to set separate watchdog timeout at startup | Tomas Ulin | ||
| 37975 | 2008-07-08 17:14 | Tests: Replication | Closed (1211 days) | S2 | 5.1+ | 5.1+ | Any | wait_for_slave_* should increase the timeout | Sven Sandberg |
| 45978 | 2009-07-06 18:42 | Connector/Net | Closed (778 days) | S2 | 5.1.36 | Microsoft Windows | Silent problem when net_write_timeout is exceeded | Reggie Burnett | |
| 55309 | 2010-07-16 7:04 | Tools: Random Query Generator | Verified (679 days) | S2 | bzr-revno481 | Microsoft Windows | RQG: Out Of Memory issues on Windows with runall-new.pl | Bernt Johnsen | |
| 15211 | 2005-11-24 3:08 | Connector/ODBC | Duplicate (1906 days) | S2 | 3.51.12 | Microsoft Windows (Window XP) | ODBC timeouts can't be change with MyODBC! | ||
| 60425 | 2011-03-11 2:58 | Server: Replication | Not a Bug (127 days) | S3 | mysql5.5 | Any | The rpl_semi_sync_master_wait_no_slave variable is invalid |
| Showing 1-100 of 2733 (Edit, Save, CSV, Feed) | Show Next 100 Entries » |
