[MDEV-16033] rocksdb.deadlock fails in buildbot with timeout Created: 2018-04-25  Updated: 2023-04-27

Status: Open
Project: MariaDB Server
Component/s: Storage Engine - RocksDB, Tests
Affects Version/s: 10.2, 10.3
Fix Version/s: 10.4

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Sergei Petrunia
Resolution: Unresolved Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-deb-trusty-amd64/builds/10324/steps/mtr/logs/stdio

rocksdb.deadlock                         w3 [ fail ]  timeout after 900 seconds
        Test ended at 2018-04-25 01:44:30
 
Test case timeout after 900 seconds
 
== /run/shm/var/3/log/deadlock.log == 
#
# Validate that deadlock errors don't occur with a high level of concurrency
#
# Disable for valgrind because this takes too long
DROP DATABASE IF EXISTS mysqlslap;
CREATE DATABASE mysqlslap;
USE mysqlslap;
CREATE TABLE t1(id1 BIGINT, id2 BIGINT, count INT, PRIMARY KEY(id1, id2), KEY(id2)) ENGINE=rocksdb;
CREATE TABLE t1rev(id1 BIGINT, id2 BIGINT, count INT, PRIMARY KEY(id1, id2) COMMENT "rev:cf2", KEY(id2) COMMENT "rev:cf2") ENGINE=rocksdb;
SET @save = @@global.rocksdb_lock_wait_timeout;
SET GLOBAL rocksdb_lock_wait_timeout = 60;
SELECT count from t1;
count
50000
SELECT count from t1;
count
100000
SELECT count from t1;
count
150000
 
 == /run/shm/var/3/tmp/analyze-timeout-mysqld.1.err ==
mysqltest: Could not open connection 'default': 2013 Lost connection to MySQL server at 'handshake: reading inital communication packet', system error: 110

Not the first time, according to cross-reference.



 Comments   
Comment by Sergei Petrunia [ 2018-10-09 ]

Was still happening in September and October.

Generated at Thu Feb 08 08:25:51 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.