On Jun 20, 2005, at 5:37 PM, Kevin Burton wrote:
Kevin Burton wrote:
We're noticing a problem where if we were to write to the master
with multiple threads that our slave DB will fall behind.
BTW.. I should clarify.. when I mean "break" I really meant to say
that the slave replication will fall WAY behind because it can't
replay transactions as fast as the master. So if your slave is 10k
seconds behind its essentially "broken" .
Yes, that will happen b/c replication uses only a single query
execution process. However, the queries are still being copied to
the slave, they are just queued for execution.
It depends on what you are using replication for as to whether you'd
call it broken. It still works fine for disaster recovery in a lot
of instances, b/c the queries are safely on the slave for execution
even if the master dies.
--Ware
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
