Comments - Global Transaction ID
Content reproduced on this site is the property of its respective owners,
and this content is not reviewed in advance by MariaDB. The views, information and opinions
expressed by this content do not necessarily represent those of MariaDB or any other party.
I've noticed that GTID Strict Mode causes issues in a master - master replication, when running an optimization task for all databases.
When executing the command "--auto-repair --optimize --all-databases" on server A. This results in the following error on server B: Last_SQL_Error: An attempt was made to binlog GTID 10-10-69958886 which would create an out-of-order sequence number with existing GTID 10-10-69958886, and gtid strict mode is enabled
Is this a bug or expected behaviour?