With regard to mysql master-slave replication, the master library restarts the log-bin file, position changes, can only manually update the slave library?

background: Ali CVM, multiple instances of mysql built on a single host

question: when tampering with master-slave replication, it is found that the log-bin file and position will change with the restart of the master library. Can only manually update the MASTER_LOG_FILE and MASTER_LOG_POS of the slave library? Do you bosses have a good and mature solution?

Linux-operation-and-maintenance php mysql--configure mysqldb mysql-master-slave

Jun.01,2022

the master library is restarted, and when the slave library is automatically reconnected, it will automatically keep up with the binlog location of the master library. If there is no automatic connection, just stop slave;start slave manually

restart the master library

to sum up, the slave library will retry to connect to the master library for 60s by default to keep the data synchronized!

Previous: The front and rear ends are separated to determine the source of the request.

Next: Can php grab APP data?

MySQL Query : SELECT * FROM `codeshelper`.`v9_news` WHERE status=99 AND catid='6' ORDER BY rand() LIMIT 5
MySQL Error : Disk full (/tmp/#sql-temptable-64f5-1b371fe-2c071.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
MySQL Errno : 1021
Message : Disk full (/tmp/#sql-temptable-64f5-1b371fe-2c071.MAI); waiting for someone to free some space... (errno: 28 "No space left on device")
Need Help?