[MDEV-12285] MariaRocks: [ERROR] mysqld: Deadlock found when trying to get lock messages in server stderr Created: 2017-03-16  Updated: 2017-03-16  Resolved: 2017-03-16

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - RocksDB
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: Sergei Petrunia Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
PartOf
is part of MDEV-9658 Make MyRocks in MariaDB stable Closed

 Description   

A number of tests started to fail recently like this:

./mtr rocksdb.locking_issues
 
....
 
worker[1] Using MTR_BUILD_THREAD 300, with reserved ports 16000..16019
 
rocksdb.locking_issues                   [ fail ]  Found warnings/errors in server log file!
 
        Test ended at 2017-03-16 19:50:00
 
line
 
2017-03-16 19:47:40 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
 
2017-03-16 19:48:58 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
 
2017-03-16 19:49:38 140286479893248 [ERROR] mysqld: Deadlock found when trying to get lock; try restarting transaction
 
^ Found warnings in /home/psergey/dev-git/10.2-mariarocks/mysql-test/var/log/mysqld.1.err
 
ok



 Comments   
Comment by Sergei Petrunia [ 2017-03-16 ]

The warnings are now visible, because log_warnings=2 after this change:
https://github.com/MariaDB/server/commit/3435e8a51552c3c73feab4b1c731dd8da225618c

If I take an older server and put 

set log_warnings=2;
 
set global log_warnings=2;

at the top of locking_issues.test, I get the same warnings.

Comment by Sergei Petrunia [ 2017-03-16 ]

Disabled the warnings in bb-10.2-mariarocks tree

Generated at Thu Feb 08 07:56:32 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.