Question 580
The service owner asks how to avoid a repeat of: A MySQL source fills its disk because its binary logs accumulate during a slow long-running migration. Which operational check is the best match?
Explanation
Correct Answer
Monitor binary log storage and purge dependencies throughout continuous replication. This is preventive rather than a one-time repair; it addresses the underlying failure: Binary log retention was increased without sizing the source's available storage and CDC duration.
Incorrect Answers
The failure in the question arises because binary log retention was increased without sizing the source's available storage and CDC duration. A safeguard to treat bidirectional replication as an explicitly tested design, not an automatic fallback serves situations where engineers enable reverse replication from a new database to the old system without checking schema divergence rather than this one.
This would use peak write windows to stress-test continuous migration capacity. It is useful when a managed migration reports low steady-state lag but a nightly batch produces a huge backlog and threatens cutover, but it does not prevent the issue here: binary log retention was increased without sizing the source's available storage and CDC duration.
This control would include migration jobs in all source-credential rotation inventories; it responds to the risk in which a migration connection fails after a source password rotation, while ordinary applications continue using new credentials. It would not address the current root cause: binary log retention was increased without sizing the source's available storage and CDC duration.