I have set up MYSql Replication using 2x 128gig ram 24 core cloud servers. we have a massive live database that cannot experience down time due to the high volume of data input.
I have found while dealing with the master slave is if I restart the service the bin_log and position change. Thus the slave needs to be updated and even then will be missing the data for the period it did not have the new bin_log set.
Dealing with my database which is over 400 gigs big, and is required to be live 99% of the time I cannot afford to Lock tables, Dump, transfer and import.
The slave is also very impotent as all reads are done from it and the data is highly relevant to current user interaction and as such cannot experience missing data or down time.
Moreover I am using mysql 5.5
So my questions are as follows:
1) What else if anything can cause the bin_log on the master to change. 2) How can I get my slave to consolidate and catch up the missing data without redoing the whole slave.
Any help will be highly appreciated.