FW: 4.0.20 replication

Excuse the forward...

I didn't hit reply all - forgive the intrusion if I'm wrong about my
response, below.

Respectfully, 
michael
> -----Original Message-----
> From: DePhillips, Michael P
> Sent: Friday, June 18, 2004 9:50 AM
> To: '[email protected]'
> Subject: RE: 4.0.20 replication
> 
> > ok, that explains it.
> 
> No it doesn't.
> 
> > Otherwise, each time a slave connects to the master, it will stop the
> > replication of all other threads; because master will believe that the
> > same slave is connecting twice (or more), whereas only one connection
> > is needed by slave, so it will kill all "useless" connections.
> 
> This is the opposite of what is happening.  The threads are NOT being
> killed. They are remaining and new threads are being created.
> 
> I understand this, and it hasn't mattered (all worked fine) until 4.0.20
> which is why I submitted a bug report.  If what you say is correct then my
> only adverse affect of this configuration is that each mirror reconnects,
> fine.  THE BUG (I respect the sanctity of a bug-list) is that the
> CONNECTIONS REMAIN. They should not.  I understand that this is not easy
> to guard against but it is not impossible and it indeed will crash servers
> unless checked, this is why I reported it here.
> 
> Again to be clear and concise this....
> 
> >  because master will believe that the
> > same slave is connecting twice (or more), whereas only one connection
> > is needed by slave, so it will kill all "useless" connections.
> ....
> Is not working.
> 
> Thanks for your help.
> Michael
> 
> > -----Original Message-----
> > From: Sinisa Milivojevic [mailto:[email protected]]
> > Sent: Friday, June 18, 2004 9:43 AM
> > To: DePhillips, Michael P
> > Cc: [email protected]
> > Subject: RE: 4.0.20 replication
> >
> > >  Hi -
> > >
> > > The serverIDs are the _same_ on all the slaves but they (as a group)
> > differ
> > > from the master.
> >
> > ok, that explains it.
> > Server ids must be different on all slaves of the same master.
> > Otherwise, each time a slave connects to the master, it will stop the
> > replication of all other threads; because master will believe that the
> > same slave is connecting twice (or more), whereas only one connection
> > is needed by slave, so it will kill all "useless" connections.
> > Will emphasize it in the manual.
> >
> > Please keep in mind that this list is dedicated to true bugs with
> > repeatable test cases.
> >
> > It is not to be used for free support, like in this case.
> >
> > --
> >
> > Sincerely,
> >
> > --
> > For technical support contracts, go to https://order.mysql.com/?ref=msmi
> >    __  ___     ___ ____  __
> >   /  |/  /_ __/ __/ __ \/ /    Mr. Sinisa Milivojevic <[email protected]>
> >  / /|_/ / // /\ \/ /_/ / /__   MySQL AB
> > /_/  /_/\_, /___/\___\_\___/   Full time Developer and Support
> Coordinator
> >        <___/   www.mysql.com   Larnaca, Cyprus


-- 
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe:    http://lists.mysql.com/[email protected]