CHANGING "MASTER_DELAY" AFTER STOP SLAVE RESULTS IN LOSS OF EVENTS

CHANGING "MASTER_DELAY" AFTER STOP SLAVE RESULTS IN LOSS OF EVENTS (Doc ID 2240404.1)

Last updated on MARCH 06, 2017

Applies to:

MySQL Server - Version 5.7 and later
Information in this document applies to any platform.

Changing the replication delay with :

causes the slave to apply events from the wrong binary log position.

	Sign In with your My Oracle Support account
	Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms