[mysql-zrm-users] Stop Slave

[Mathieu Bruneau]

After rethinking of this mail, I realized I made a small mistake: it's
actually the SQL_THREAD not the IO_THREAD that I was thinking here. Also
I found that this syntax is supported since 4.0.2 which means it would
be the lower boundary for this usage. I'm sure people using 4.0 in
production are wise enough to use more recent 4.0 version tough...

As a note, that would mean changing the stopSlave sub to using mysql
client instead of the mysqladmin command but I don't think that would be
a real problem...


-- 
Math
aka ROunofF

======
argontechnologies.ca


Mathieu Bruneau a écrit :
> Heya,
> 	One of the thing I don't like at the moment for backing up a database
> (using a replicate slave) is that you cut all connection to the master
> with STOP SLAVE.
> 
> 	Since what we only need to do is prevent write to the database, I think
> it could be envisageable to issue simply a STOP SLAVE IO_THREAD to
> simply cut the IO_THREAD from playing the sql.
> 
> 	This has a simple advantage that the binlog are still transferred from
> the master and in the infortunate event that your master _burn_ you
> still have access to your binlog to play them. (Small chance but hey!)
> 
> 	The syntax for STOP SLAVE IO_THREAD seems to be the same since 4.0 so I
> think it's possibly a feature/option that could be usefull! I prefer to
> talk about it in here before actually posting it as a feature request
> inside bugzilla!
> 
> 	Feel free to discuss if you think there could be reason not to! Regards,
>