LevelDB storage engine (MDEV-3841)

[MDEV-4044] LevelDB: UPDATE or DELETE with ORDER BY 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: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Duplicate Votes: 0
Labels: leveldb

Issue Links:
Relates

 Description   

Test case (LIMIT clause is not needed to reproduce the problem, it just makes using ORDER BY reasonable):

--disable_abort_on_error
 
create table t1 (pk int primary key, c char(1)) engine=LevelDB;
 
insert into t1 values (1,'a'),(2,'b');
 
update t1 set c = 'x' order by pk limit 1;
 
delete from t1 order by pk limit 1;
 
select * from t1;

Output:

create table t1 (pk int primary key, c char(1)) engine=LevelDB;
 
insert into t1 values (1,'a'),(2,'b');
 
update t1 set c = 'x' order by pk limit 1;
 
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
 
delete from t1 order by pk limit 1;
 
ERROR HY000: Lock wait timeout exceeded; try restarting transaction
 
select * from t1;
 
pk      c
 
1       a
 
2       b
 

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-4046 come from the same basic (known) problem as below, and just need 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 ]

Also fixed by MDEV-4047.

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