Submitted by Django (not verified) on Thu, 2009-08-13 11:50.
One thing I rarely see mentioned in replication guides is what the proper procedures are for shutting down either mysql or the whole system on a master or slave. I've had sysadmins restart slave machines and when they came back online replication did not and sometimes days of replication was missing, and at times have had trouble getting the slave to read those interim binary logs. Could you outline some best practices for shutting down mysql or whole systems when using replication?
RSS Feed
Replication best practices for shutdown/restart
One thing I rarely see mentioned in replication guides is what the proper procedures are for shutting down either mysql or the whole system on a master or slave. I've had sysadmins restart slave machines and when they came back online replication did not and sometimes days of replication was missing, and at times have had trouble getting the slave to read those interim binary logs. Could you outline some best practices for shutting down mysql or whole systems when using replication?