[MDEV-19998] SST position in the past after recovery Created: 2019-07-09  Updated: 2023-07-18  Resolved: 2021-06-24

Status: Closed
Project: MariaDB Server
Component/s: Galera, Galera SST, Storage Engine - InnoDB
Affects Version/s: 10.2, 10.3
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Julius Goryavsky Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None


 Description   

galera.galera_autoinc_sst_mariabackup-innodb (and some other tests sometime) is failed due to SST position in the past after recovery:

2019-07-09  9:32:12 0 [Note] Recovering after a crash using tc.log
 
2019-07-09  9:32:12 0 [Note] Starting crash recovery...
 
2019-07-09  9:32:12 0 [Note] InnoDB: Starting recovery for XA transactions...
 
2019-07-09  9:32:12 0 [Note] InnoDB: Transaction 23350 in prepared state after recovery
 
2019-07-09  9:32:12 0 [Note] InnoDB: Transaction contains changes to 1 rows
 
2019-07-09  9:32:12 0 [Note] InnoDB: 1 transactions in prepared state after recovery
 
2019-07-09  9:32:12 0 [Note] Found 1 prepared transaction(s) in InnoDB
 
2019-07-09  9:32:12 0 [Note] WSREP: Last wsrep seqno to be recovered 11663
 
2019-07-09  9:32:12 0 [Note] Crash recovery finished.
 
2019-07-09  9:32:12 0 [Note] Server socket created on IP: '127.0.0.1'.
 
2019-07-09  9:32:12 0 [Note] WSREP: Signalling provider to continue.
 
2019-07-09  9:32:12 0 [Warning] WSREP: SST position can't be set in past. Requested: 11421, Current:  11663.
 
2019-07-09  9:32:12 0 [Warning] WSREP: Can't continue.
 
2019-07-09  9:32:12 0 [ERROR] Aborting



 Comments   
Comment by Jan Lindström (Inactive) [ 2021-06-24 ]

Fixed on SST script cleanup.

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