[prev in list] [next in list] [prev in thread] [next in thread] 

List:       mysql-bugs
Subject:    Re: Replication does not continue after removal/replace of network cable.
From:       Sasha Pachev <sasha () mysql ! com>
Date:       2001-03-26 22:27:22
[Download RAW message or body]

On Monday 26 March 2001 08:16, Johan Vanroose wrote:
> Jean-Luc Fontaine wrote:
> 
> > On Monday 26 March 2001 12:19, Johan Vanroose wrote:
> > > Jean-Luc Fontaine wrote:
> > > > On Thursday 22 March 2001 16:46, Johan Vanroose wrote:
> > > > > From: johan.vanroose@alcatel.be
> > > > > To:   mysql-win32@lists.mysql.com
> > > > > Subject: Replication does not continue after removal/replace of 
network
> > > > > cable.
> > > > >
> > > > > Description:
> > > > >  Configuration.
> > > > >  Two servers (PCs) running mysql, both are master and slave to each
> > > > > other.
> > > > >  Replication using binary log.
> > > > >  Updates done (from the mysql console) on either server are 
replicated
> > > > > to the other.
> > > > >  (The application (I) takes care that the updates are not 
conflicting.)
> > > > >  So far so good.
> > > > >  Now the problem.
> > > > >  I remove a network cable from one of the servers.
> > > > >  I do an update (insert into table) on server 1.
> > > > >  I do a second update (again insert) on server 2.
> > > > >  Of course the updates aren't replicated (no communication 
possible).
> > > > >  However... when I replace the cable, the replication is not done 
for
> > > > > the
> > > > >  previous two inserts. I waited 4 minutes... Still no replication.
> > > >
> > > > Hmmm. The same thing happened to me with the 3.23.35 rpm on Linux 
Redaht
> > > > 7.0. I had to do a 'slave stop/start' for the slave to recover.

Just tested the above issue with the master running on RH 6.1 and the slave 
on Suse 7.0 both running 3.23.33 - worked just fine - the update showed up on 
the slave within the amount of time it took me to sit up after putting the 
cable back in, hit up arrow in the MySQL client followed by enter - about 5 
seconds after plugging the cable back in.

I realize it is difficult to create a repeatable test case here, but it would 
as least help if you could provide the output of show processlist, show slave 
status and show master status, any messages in the error log, and if you 
could also sniff on both master and slave interfaces and capture all traffic 
between the master and the slave. On Linux, to sniff you could use tcpdump - 
use -w argument to get raw packets, and make sure to filter - otherwise the 
file will get big very quick if your network is even medium-busy.

-- 
MySQL Development Team
   __  ___     ___ ____  __ 
  /  |/  /_ __/ __/ __ \/ /   Sasha Pachev <sasha@mysql.com>
 / /|_/ / // /\ \/ /_/ / /__  MySQL AB, http://www.mysql.com/
/_/  /_/\_, /___/\___\_\___/  Provo, Utah, USA
       <___/                  

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail bugs-thread1169@lists.mysql.com
To unsubscribe, e-mail <bugs-unsubscribe@lists.mysql.com>

[prev in list] [next in list] [prev in thread] [next in thread]