Error 1951: The binlog on the master is missing the GTID requested by the slave

You are viewing an old version of this article. View the current version here.
Error CodeSQLSTATEErrorDescription
1951ER_GTID_START_FROM_BINLOG_HOLEThe binlog on the master is missing the GTID %u-%u-%llu requested by the slave (even though a subsequent sequence number does exist), and GTID strict mode is enabled

Possible Causes and Solutions

This article doesn't currently contain any content. You can help!

Comments

Comments loading...
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.