[MDEV-16954] gcol.gcol_rollback failed in buildbot with Unknown storage engine 'InnoDB' Created: 2018-08-12  Updated: 2020-07-09  Resolved: 2020-07-09

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB, Tests
Affects Version/s: 10.2
Fix Version/s: 10.2.17

Type: Bug Priority: Major
Reporter: Elena Stepanova Assignee: Thirunarayanan Balathandayuthapani
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-16273 innodb.alter_kill fails in buildbot w... Closed

 Description   

Note: possibly related to MDEV-16273 and/or 12905.

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos6-amd64-debug/builds/691

gcol.gcol_rollback 'innodb'              w3 [ fail ]
 
        Test ended at 2018-08-10 17:22:44
 
 
 
CURRENT_TEST: gcol.gcol_rollback
 
mysqltest: At line 36: query 'SELECT * FROM t' failed: 1286: Unknown storage engine 'InnoDB'
 
 
 
The result from queries just before the failure was:
 
< snip >
 
DELETE FROM t where a = 12;
 
ROLLBACK TO SAVEPOINT a;
 
COMMIT;
 
CHECK TABLE t;
 
Table	Op	Msg_type	Msg_text
 
test.t	check	status	OK
 
SELECT * FROM t;
 
a	b
 
9	9
 
BEGIN;
 
INSERT INTO t (a) VALUES (10);
 
SELECT * FROM t;



 Comments   
Comment by Elena Stepanova [ 2018-08-12 ]

Possibly fixed by the next commit

commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a
 
Author: Marko Mäkelä <marko.makela@mariadb.com>
 
Date:   Fri Aug 10 17:01:53 2018 +0300
 
 
 
    Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a
 
    
    recv_parse_log_recs(): Do not check for corruption before
 
    checking for end-of-log-buffer. For some reason, adding the
 
    check to the logical-looking place would cause intermittent
 
    recovery failures in the tests innodb.innodb-index and
 
    innodb_gis.rtree_compress2.

Comment by Thirunarayanan Balathandayuthapani [ 2020-07-09 ]

I don't see any failure of gcol.gcol_rollback in cross-reference after 2018-08-10. I would like to close this bug. Looks like the following patch fixed the issue:

commit 29150e23912ef6e1fe386f53b778c9a5551c4790 b853b4fd88b441f36eeb7eabdce79918ef10538a
 
 
 
Author: Marko Mäkelä <marko.makela@mariadb.com>
 
Date:   Fri Aug 10 17:01:53 2018 +0300
 
 
 
Revert part of b853b4fd88b441f36eeb7eabdce79918ef10538a

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