MySQL master slave replica interrupts after service restart or reboot

Apr 26, 2022
Reaction score
I've been using the master slave replica to keep a mySQL database and its disaster recovery perfectly aligned.

I noticed that unfortunately every time the mySQL service restarts, or one of the server is rebooted, the replica stops to work and I need to reactivate it manually.

Maybe this behavior is normal and acceptable in some kind of scenario, but in a real working environment this is not reliable and sustainable.

I need to understand if there is any option to avoid this interruption, or some way to automatize the restart. When I launch the "show master status" command, I noticed that the master log file ("file" column) is incremental, but the master log position ("position" column) is not. Is there any way to control this parameters? Or is there any other reliable process more than master slave replica, in a mySQL environment?

Many thanks in advance, Kind regards

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question