Hi.
On Thu, Dec 13, 2001 at 11:57:35AM +0000, [EMAIL PROTECTED] wrote:
> Hi all,
>
> This is in regard to setting up replication, I do not wish to shut down
> the master so I noticed I can do "FLUSH TABLES WITH READ LOCK" and then
> tar up the databases.
>
> I tried this on a non-critical machine and while the READ LOCK is on it
> does not deny operations on the database, just seems to cache them until I run
> UNLOCK TABLES.
Correct. There is no timeout related to LOCKs.
> My worry is, how many commands can it spool like that?
As much as your max_connection variable allows.
> I have to copy across a snapshot database to a slave that is about 700M
> and tarring is it up my take a while,
You could copy it to another disk, which should be quite fast, release
the lock and then tar the copied files.
> so I am worried about all those database operations queing up,
> should I be?
Yes.
> Will mysql handle the waiting queries well?
Not really. If you get a fair amount of traffic, max_connection will
be reached soon.
Bye,
Benjamin.
> I include details on my setup at end.
>
> Regards, Fred.
>
> System Info:
>
> MySQL version - 3.23.40
> OS - Linux 2.2.14
> CPU - P3 550Mhz
> Memory - 128M
[...]
--
[EMAIL PROTECTED]
---------------------------------------------------------------------
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 <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
