LevelDB storage engine (MDEV-3841)

[MDEV-4046] LevelDB: Multi-table DELETE locks itself and ends with ER_LOCK_WAIT_TIMEOUT Created: 2013-01-15  Updated: 2013-01-15  Resolved: 2013-01-15

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Technical task Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Fixed Votes: 0
Labels: leveldb

Issue Links:
Relates

 Description   

Test case:

CREATE TABLE t1 (pk int primary key) ENGINE=LevelDB;
 
INSERT INTO t1 VALUES (1),(2);
 
 
 
CREATE TABLE t2 LIKE t1;
 
INSERT INTO t2 SELECT * FROM t1;
 
 
 
DELETE t2.* FROM t1, t2;

Output:

CREATE TABLE t1 (pk int primary key) ENGINE=LevelDB;
 
INSERT INTO t1 VALUES (1),(2);
 
CREATE TABLE t2 LIKE t1;
 
INSERT INTO t2 SELECT * FROM t1;
 
main.t1                                  [ fail ]
 
        Test ended at 2013-01-15 04:13:16
 
 
 
CURRENT_TEST: main.t1
 
mysqltest: At line 8: query 'DELETE t2.* FROM t1, t2' failed: 1205: Lock wait timeout exceeded; try restarting transaction
 

revision-id: psergey@askmonty.org-20130114195003-fgp08gh4swgcf1cx
 
revno: 4486
 
branch-nick: mysql-5.6-leveldb



 Comments   
Comment by Elena Stepanova [ 2013-01-15 ]

Possibly both this and MDEV-4044 come from the same basic (known) problem as below, and just needs to wait till it's fixed

create table t1 (i int primary key) engine=leveldb;
insert into t1 values (1),(1);
ERROR HY000: Lock wait timeout exceeded; try restarting transaction

Comment by Sergei Petrunia [ 2013-01-15 ]

Fixed by fix for MDEV-4047. Added a testcase.

Generated at Thu Feb 08 06:53:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.