Bug 47096 fixed the problem of LOST_EVENTS not being generated on an restart of an SQL node operating as the master. Now that it's being generated properly, is there a way to optionally prevent the LOST_EVENTS from being generated on a restart? We have controlled situations where we need to reboot a machine that is operating as the master when we know there will be no database changes to the cluster during that time. Failing over the slaves to the secondary channel or reissuing the change master command is unnecessary overhead when we just need to restart the master. I was hoping there would be a command line option that could be specified during this controlled restart that would prevent the LOST_EVENTS from being generated. During normal operations any master restart would be done without this option so the LOST_EVENTS is generated.
↧