Skip to content
This repository was archived by the owner on Feb 18, 2025. It is now read-only.

Skip RestartReplicationQuick() on MariaDB with GTID#1264

Merged
shlomi-noach merged 3 commits intomasterfrom
mariadb-gtid-io-thread
Nov 19, 2020
Merged

Skip RestartReplicationQuick() on MariaDB with GTID#1264
shlomi-noach merged 3 commits intomasterfrom
mariadb-gtid-io-thread

Conversation

@shlomi-noach
Copy link
Collaborator

Fixes #1260

In MariaDB GTID, stopping and starting IO thread actually deletes relay logs. This is counter productive to our objective.

Specifically, in a situation where the primary is unreachable and where replicas are lagging, we want to restart IO thread to see if lag is actually caused by locked primary. If this results with losing relay logs, then we've lost data.

So, unfortunately we avoid this step in MariaDB GTID.

cc @pedroalb

@shlomi-noach shlomi-noach merged commit f17c442 into master Nov 19, 2020
@shlomi-noach shlomi-noach deleted the mariadb-gtid-io-thread branch November 19, 2020 15:59
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Orchestrator prematurely promotes lagging replica when configured with MariaDB GTID

2 participants