Re: mysql as cluster service, failover causes broken replication

2004-03-25 Thread Sasha Pachev
Matt Sturtz wrote: Yes, the clients (appearently) read to the end of the previous file, and then sit there, while the server is writing to a new file. I was thinking this had to do with the "unclean" shutdown of MySQL-- perhapps it's something else. It might, but it is a bug anyway. The whole idea

Re: mysql as cluster service, failover causes broken replication

2004-03-25 Thread Matt Sturtz
Yes, the clients (appearently) read to the end of the previous file, and then sit there, while the server is writing to a new file. I was thinking this had to do with the "unclean" shutdown of MySQL-- perhapps it's something else. -Matt- > Matt Sturtz wrote: >> Hello-- >> >> We're using Red Hat

Re: mysql as cluster service, failover causes broken replication

2004-03-24 Thread Sasha Pachev
Matt Sturtz wrote: Hello-- We're using Red Hat's cluster manager (RH AS 2.1, MySQL 4.0.16 RPM). Due to a problem within the cluster software that we're working on with Red Hat, the cluster fails over from one node to the other sometimes when it shouldn't (one node will reboot, services will fail

mysql as cluster service, failover causes broken replication

2004-03-22 Thread Matt Sturtz
Hello-- We're using Red Hat's cluster manager (RH AS 2.1, MySQL 4.0.16 RPM). Due to a problem within the cluster software that we're working on with Red Hat, the cluster fails over from one node to the other sometimes when it shouldn't (one node will reboot, services will fail over-- at this poin