10 messages in com.mysql.lists.bugsRe: Replication problem 1)
FromSent OnAttachments
PeterWR13 Jun 2001 20:02.zip
Sasha Pachev14 Jun 2001 10:09 
Sasha Pachev14 Jun 2001 12:32 
Michael Widenius15 Jun 2001 01:40 
PeterWR15 Jun 2001 02:17 
Sasha Pachev15 Jun 2001 07:36 
Peter01 Aug 2001 15:19 
Sasha Pachev02 Aug 2001 10:48 
Miguel Angel Solórzano02 Aug 2001 12:34 
Peter02 Aug 2001 16:42 
Subject:Re: Replication problem 1)
From:Peter (pw@post4.tele.dk)
Date:08/01/2001 03:19:25 PM
List:com.mysql.lists.bugs

Hi,

Coming back to this issue - will vers. 3.23.40 "Added slave_wait_timeout for replication" solve my problem on Windows environment for automatic/manually closing down slave ?

How is "mysql.org" going - I can see You latest posting is July 16th on www.mysql.com ?

Hi!

"Sasha" == Sasha Pachev <sas@mysql.com> writes:

Sasha> On Wednesday 13 June 2001 21:02, PeterWR wrote:

Hi,

I have a problem setting up a internal replication between a Win2000

server

Sasha> SP2 (MASTER) and a WinNT4 SP5 (SLAVE). I dont know if this is a bug or just Sasha> me ...!

Sasha> SLAVE STOP is broken on Windows. The problem is that on Windows if a thread Sasha> is in the middle of I/O, there is no easy way known to us to communicate to Sasha> it that it is supposed to return from the I/O call with an error, and we have Sasha> not yet come up with a viable workaround for this.

Sasha, how about if we on windows would close the TCP/IP connection the slave thread is using on SLAVE STOP ?

Regards, Monty