On 2/10/2009 10:28 PM, J Potter wrote:
For what it's worth, I haven't seen this on any systems I manage when
going from 5.0.22-5.0.45, which include permutations of master-slave
and master-master.
Is there anything useful in /var/log/mysqld.log?
Just that I cant't read the
On 2/11/2009 12:46 AM, Jim Perrin wrote:
On Mon, Feb 9, 2009 at 7:33 AM, Alessandro Ren
alessandro@opservices.com.br wrote:
e incremental.01 on
the master and this causes the problem.
In 5.0.22 this would not happen, this does not happen as I have
servers running this version
For what it's worth, I haven't seen this on any systems I manage when
going from 5.0.22-5.0.45, which include permutations of master-slave
and master-master.
Is there anything useful in /var/log/mysqld.log?
after I updated from mysql-5.0.22 CentOS 5.0 to mysqld-5.0.45 in
CentOS
5.2,
On Mon, Feb 9, 2009 at 7:33 AM, Alessandro Ren
alessandro@opservices.com.br wrote:
e incremental.01 on
the master and this causes the problem.
In 5.0.22 this would not happen, this does not happen as I have
servers running this version and after the reboot, it starts syncing on
the
Hello,
after I updated from mysql-5.0.22 CentOS 5.0 to mysqld-5.0.45 in CentOS
5.2, mysql looses master-slave sync after one node reboots.
I've noticed that the slave doest not respect the informantion on
master.info, instead, it tries to read the informantion from the master
server
5 matches
Mail list logo
