Jonathan Tullett wrote:
> Further to the email below,I performed the upgrade last night and we are
> now running mysql 4.0.16.
> the last on the syncronization hasnt reduced any, so if anyone knows how
> else I can keep these two databases in sync, I would be very interested
> in knowing how!
> now that we are running the 4.0 series, I would hope our options for
> this will be increased!
> thanks in advance for any help you can provide...
I don't know if this is related to the problems you are having, but I am
using 4.0.17 on RedHat 7.3 (both ends) and was experiencing that the
slave would just stop replicating after a while. No errors, it just sat
there doing nothing. Replication would happen perfectly for a while, but
then when I go away and come back after a few hours it was behind again.
I made the situation better by changing the timeouts on the slave end
After this the slave seemed to stay up, but I am now having different
problems - occasional lost updates on the master (!) - I would post a
message on a board, and a bit later it was gone. This on software that's
been running just fine for years. Also, I am getting "duplicate key"
errors on the slave occasionally, even though no changes happen on the
slave. Obviously the replication in MySQL at the moment is not as robust
as it should be. No data should get lost on the master as a result of
replication in any circumstances, and there is no reason for the slave
to get out of sync... I have had no replies from my original emails
about this, so I am trying to build MySQL from source to see if it makes
any difference. I'll post more on that saga a bit later.
Anyway, maybe the net timeout config stuff will help your setup...
All the best,