[MDEV-24446] galera.mysql-wsrep#198 MTR failed: query 'reap' failed: 2000: Unknown MySQL error Created: 2020-12-18  Updated: 2022-01-20  Resolved: 2022-01-19

Status: Closed
Project: MariaDB Server
Component/s: Galera, Tests
Affects Version/s: 10.3.28, 10.4.18
Fix Version/s: 10.4.23, 10.5.14, 10.6.6, 10.7.2

Type: Bug Priority: Major
Reporter: Stepan Patryshev (Inactive) Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Environment:

kvm-deb-stretch-x86


Attachments: Zip Archive MDEV-24446_10_4_logs_201203.zip    

 Description   

galera.mysql-wsrep#198 failed on BB 10.4 CS: "query 'reap' failed: 2000: Unknown MySQL error".
It seems to be a sporadic issue.

stdio.log:

10.4.18, a50cb4867a7f63bfc03b33bfb5be8d47d15ba64d, kvm-deb-stretch-x86

galera.mysql-wsrep#198 'innodb'          w1 [ fail ]
        Test ended at 2020-12-03 06:01:23
 
CURRENT_TEST: galera.mysql-wsrep#198
mysqltest: At line 34: query 'reap' failed: 2000: Unknown MySQL error
 
The result from queries just before the failure was:
< snip >
connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
connection node_2a;
OPTIMIZE TABLE t1,t2;;
connect node_2b, 127.0.0.1, root, , test, $NODE_MYPORT_2;
connection node_2b;
REPAIR TABLE t1,t2;;
connection node_2;
SET SESSION wsrep_sync_wait = 0;
connection node_1;
INSERT INTO t2 VALUES (1);
connection node_2;
UNLOCK TABLES;
connection node_2a;
 
More results from queries before failure can be found in /dev/shm/var/1/log/mysql-wsrep#198.log
 
 - saving '/dev/shm/var/1/log/galera.mysql-wsrep#198-innodb/' to '/dev/shm/var/log/galera.mysql-wsrep#198-innodb/'
 
Retrying test galera.mysql-wsrep#198, attempt(2/3)...
 
worker[1] > Restart  - not started
worker[1] > Restart  - not started
galera.mysql-wsrep#198 'innodb'          w1 [ retry-pass ]   2128
 
Retrying test galera.mysql-wsrep#198, attempt(3/3)...
 
worker[1] > Restart  - not started
worker[1] > Restart  - not started

Server logs.



 Comments   
Comment by Stepan Patryshev (Inactive) [ 2021-02-12 ]

It failed on BB 10.3 CS with another output: "query 'INSERT INTO t2 VALUES (1)' failed: 1062: Duplicate entry '1' for key 'PRIMARY'".

stdio.log:

10.3.28, eaeb8ec4b87882711ecb8e1c7476a6e410d5d2a9, kvm-deb-stretch-amd64

galera.mysql-wsrep#198 'innodb'          w1 [ fail ]
        Test ended at 2021-01-25 06:13:15
 
CURRENT_TEST: galera.mysql-wsrep#198
mysqltest: At line 27: query 'INSERT INTO t2 VALUES (1)' failed: 1062: Duplicate entry '1' for key 'PRIMARY'
 
The result from queries just before the failure was:
CREATE TABLE t1 (id INT PRIMARY KEY) ENGINE=InnoDB;
CREATE TABLE t2 (id INT PRIMARY KEY) ENGINE=InnoDB;
connection node_2;
SELECT 1 FROM DUAL;
1
1
LOCK TABLE t2 WRITE;
connect node_2a, 127.0.0.1, root, , test, $NODE_MYPORT_2;
connection node_2a;
OPTIMIZE TABLE t1,t2;;
connect node_2b, 127.0.0.1, root, , test, $NODE_MYPORT_2;
connection node_2b;
REPAIR TABLE t1,t2;;
connection node_2;
SET SESSION wsrep_sync_wait = 0;
connection node_1;
INSERT INTO t2 VALUES (1);
 
 - saving '/dev/shm/var/1/log/galera.mysql-wsrep#198-innodb/' to '/dev/shm/var/log/galera.mysql-wsrep#198-innodb/'
 
Retrying test galera.mysql-wsrep#198, attempt(2/3)...
 
worker[1] > Restart  - not started
worker[1] > Restart  - not started

Comment by Jan Lindström (Inactive) [ 2022-01-19 ]

Fixed in MDEV-25538

Generated at Thu Feb 08 09:30:03 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.