I have this database setup:
Master -> Slave A
I would like to accomplish the following:
Master -> Slave A -> Slave B
I have reviewed the documentation.
Slave A are both in an MSP environment, while
Slave B will be an RDS instance. I can connect to
Slave A in the MSP just fine. Master binlog files are being copied over to the instance running
Slave A. All binlog files are being kept around for a long time.
However, my database size is 1.3 TB. Thus, a
Slave A takes several hours to complete, and even longer to load into my new empty
Slave B before beginning replication. In the best case scenario, it takes ~36 hours from starting the dump to when replication can start.
I would like to use
--flush-logs, as described in the third code snippet here, to reduce the chances of having to use
CALL mysql.rds_skip_repl_error; repeatedly after I begin replication. This is especially important because there is currently no way to accomplish the equivalent of
slave-skip-errors = 1062 in RDS, and also because I'm unsure what the effect is on data consistency.
Is my assumption correct, that using
--flush-logs reduces the likelihood of duplication errors arising after replication has begun?
If it is correct, what would the effect be of using
mysqldump --single-transaction --flush-logs on
Slave A? Would it behave as a tunnel and actually flush the logs on
Master, or would it only affect the logs present on