I've seen this question, but I am not sure if the solution is right for my particular error (replication breaks after upgrading master) I upgrade my master server's mysql from 5.5.34 to 5.5.35. After ...
I have to update 2 hosts with SUSE Linux Enterprise 11 from SP2 to SP3 which implies an update from MySQL 5.0.94 to 5.5.31. The release notes state: SLE 11 SP3 introduces the upgrade of the MySQL ...
Is it possible to have running real nodes with version 2.4 and arbiter nodes with 2.0 or 1.8 in the replica set? Upgrade guides for version 2.2 and 2.4, did not tell anything about upgrading ...
I have a set up of replication with master 5.1.30 and slave 5.5.16 and the replication is working good Now i have upgraded mysql master to 5.1.47 As far as i know we have to turn off the log bin ...