diff options
| author | Andrei <andrei.elkin@mariadb.com> | 2022-02-10 19:17:06 +0200 |
|---|---|---|
| committer | Andrei <andrei.elkin@mariadb.com> | 2022-03-22 19:20:19 +0200 |
| commit | 5ccd845d51d80a2f94dc796037f6d2aef106f75d (patch) | |
| tree | c98e9770cb49bb83551c0030b5267b0df8c3b51c /sql/share | |
| parent | 35725df6e2791d19bebf0301bb9fcb6200f5b00d (diff) | |
| download | mariadb-git-5ccd845d51d80a2f94dc796037f6d2aef106f75d.tar.gz | |
MDEV-27760 event may non stop replicate in circular semisync setup
MDEV-21117 had to relax own events acceptance condition for a case
when a former semisync master server recovers after crash as the
semisync slave. That however admitted a possibility for endless event
"orbiting" in the non-strict slave gtid mode of semisync circular
setup.
The same server-id event termination is restored now for
the non-strict gtid mode to follow regular rules (that is it's ignored
unless @@global.replicate_same_server_id allows it in).
To address MDEV-21117 recovery agenda,
in the strict gtid mode and the transaction's gtid ordered strictly
greater than the current slave gtid state, the same server-id
transaction is accepted.
The gtid strict mode is safe to accept transactions even if
the slave state were not set correct by the user, e.g
at the former master.
An added test shows a typical out-of-order error at execution so
no data corruption is guaranteed in such a case.
Diffstat (limited to 'sql/share')
0 files changed, 0 insertions, 0 deletions