Feature #3821
Make federation replication more robust
Status: | Closed | Start date: | 05/27/2015 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | Documentation | |||
Target version: | Release 4.14 | |||
Resolution: | invalid | Pull request: |
Description
From this forum post:
https://forum.opennebula.org/t/federation-with-new-installed-master-and-existing-slave-issue/
It may happen that the master mysql has queries before the oned bootstrap. The slave replication should use the MASTER_LOG_POS option to ignore any query before the bootstrap.
Associated revisions
feature #3821: Add SIZE attire for each DISK
History
#1 Updated by Carlos Martín almost 6 years ago
- Status changed from New to Closed
- Resolution set to invalid
After may attempts to reproduce it following our docs, the only explanation I can come up with is the accidental omission of the --master-data option in mysqldump.