Bug #81232 | Changing master_delay after stop slave results in loss of events. | ||
---|---|---|---|
Submitted: | 29 Apr 2016 10:19 | Modified: | 1 Apr 2017 15:03 |
Reporter: | Parveez Baig | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.7 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[29 Apr 2016 10:19]
Parveez Baig
[1 Apr 2017 15:03]
Paul DuBois
Posted by developer: Noted in 5.7.19, 8.0.2 changelogs. A slave server could lose events not yet applied when MASTER_AUTO_POSITION=0, both replication threads were stopped, and the applier delay was changed using CHANGE MASTER TO MASTER_DELAY=N.
[24 May 2017 12:34]
Erlend Dahl
Bug#84249 CHANGE MASTER TO MASTER_DELAY can lead a slave to skip transactions was marked as a duplicate.