Hi.
On Thu, Dec 13, 2001 at 09:05:46AM -0500, [EMAIL PROTECTED] wrote:
[...]
> I have read the Replication section of the MySQL manual and I think I have a
> basic understanding of how the replication is being handled, but one thing I
> am a bit concerned about on the two local servers is latency.
[...]
> However, we would have no way of knowing if the slaves have been
> updated if my thinking is clear; would this be correct?
Yes.
> If so, we would just have to write the server objects to query the
> master rather than a slave from interactive objects.
Looks like a good solution to me.
The latency of directly querying the server or waiting for the slave
to update and querying it should be about the same (in the ideal case
that you know when the slave has updated).
You could know whether the client is up to date or not, by checking
for a timestamp to change. But that's not pretty.
> But, is there any guideline for how long it may take for the local
> slaves to be updated?
No. In my experience, it depends mostly on your connection latency.
On the other hand, you can simply stop replication and restart it the
other day, so pending updates would need a day... ;-)
Bye,
Benjamin.
--
[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
