[MDEV-4982] GTID looses all binlog state after crash if InnoDB is disabled Created: 2013-09-03  Updated: 2013-11-21  Resolved: 2013-11-21

Status: Closed
Project: MariaDB Server
Component/s: None
Affects Version/s: None
Fix Version/s: 10.0.7

Type: Bug Priority: Major
Reporter: Kristian Nielsen Assignee: Kristian Nielsen
Resolution: Fixed Votes: 0
Labels: gtid


 Description   

If InnoDB is disabled (and no other XA-capable engine is enabled), then the
server does not do any binlog crash recovery during restart after a crash.

This is not sufficient for GTID, as we need to recover the last GTID logged
into the binlog (so that we can know the next seq_no to assign to new GTIDs
and how to reply to connecting slaves etc.).

Thus, even in non-XA case we still need to scan the binlog and do crash
recovery, though the XA part of it can be ignored.

Same when using using_heuristic_recover().

(MyISAM of course is not crash safe, but it is still better to loose a few
seconds of state or whatever compared to all state since prior server start).

 Comments   
Comment by Kristian Nielsen [ 2013-11-21 ]

Pushed to 10.0-base.

The patch ensures that we run a limited version of binlog recovery after a
crash, even if we do not have any XA storage engine, so that the binlog state
is recovered correctly.

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