MySQL master config for replication
Submitted by Guest on Sun, 11/10/2015 - 13:44
I want to turn on master/slave replication. I figure that if I set up the master, then I can play with the slave (on our test system) to see what happens. [I only get a limited 4am maintenance window on the production system so I want to make sure I have it set correctly.]
Does the following additions to the ini file look correct ?
Regards, Tim G
Re: MySQL master config for replication
Looks OK from what I've read, but I haven't actually tried it.
Note that in 1.9 you can configure your slave database to be used for SQL reports by changing the relevant hibernate.reportingconnection properties in hibernate.properties e.g.
This can reduce the load on your master database.
Re: MySQL master config for replication
Thanks Tim: a) yes I planned to play with reporting running off the slave; and b) after more research I added "expire_logs_days = 7".
The production is now running with this recipe. I will connect the slave as soon as I can.
Regards, Tim G
Re: MySQL master config for replication
By play I assume you mean run reports...we have been running a slave since inception as a primary backup solution with secondary dumps to the cloud.
Re: MySQL master config for replication
Do you do any sort of automated monitoring to ensure the slave is up to date?
Re: MySQL master config for replication
Not automated no - I check them both - I run 2 slaves.
I must admit I should look into a script - I have done a practice fail over though and then a switch back to master as well.
In my experience learning that procedure is the most important part of running slave.