The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-15. For the latest, interactive version please visit https://mariadb.com/kb/.

Maxscale rejoin after auto-failover

Hi,

I have an issue : a former master cannot rejoin and start replicating again from another slave after a failover happened

The former master shows this in "last_IO_error" : Got fatal error 1236 from master when reading data from binary log: 'Error: connecting slave requested to start from GTID 0-2-192482, which is not in the master's binlog. Since the master's binlog contains GTIDs with higher sequence numbers, it probably means that the slave has diverged due to executing extra erroneous transactions'

Am I missing something ?

Thank you

Answer Answered by Markus Mäkelä in this comment.

Sorry for the late reply. If you can reliably reproduce this, I'd like to ask you to open a bug report on the MariaDB Jira under the MaxScale project if this still happens with the latest 2.3 version of MaxScale. This way we'll be better able to track the progress of this issue.

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.