On Wed, 2004-04-21 at 12:21, Rick Romero wrote:
> On Wed, 2004-04-21 at 12:08, Jeff Koch wrote:
The replication works like a charm. I have found the occasional problem
if the vlog table is replicated, for some reason its very prone to
duplicate records. I myself just stopped using this table and my
replication issues are all gone. 
> I just did this in Feb.
> Upgrade both systems to MySQL version 4.
> Then follow this:
> http://dev.mysql.com/doc/mysql/en/Replication.html
> I personally did the LOAD DATA FROM MASTER to get the initial data set
> over to the slave.  I also put some settings into the local /etc/my.cnf
> - I kept typing commands wrong within MySQL ;)
> I had a hell of a time trying to get a Master 3.x server, and a slave
> 4.x.  I strongly recommend going with 4.x on both boxes.  Once I
> upgraded the master, everything went smoothly.
What problems did you have? I ran a 3.x master with 4.x slaves for a
while during a migration I did on my infrastructure. Obviously load data
from master isn't supported, so I had to go with the less than ideal
tar'ing under a read lock of the database files, however it was do-able.
> Rick
> > Thanks in advance for the advice and counsel.
> > 
> > 
> > Jeff Koch 
Also, if anybody here also uses big brother to monitor their servers,
I've got a perl extension I wrote for monitoring mysql replication that
works for MySQL 4.x (monitors both the IO thread and the sql thread).

Hope that helps,

Reply via email to