On Thu, Mar 5, 2009 at 10:59 AM, Jeff <threshar at torgo.978.org> wrote:

> Now, (before you all start saying "bah, buy more disks") things are fine
> under low load or smaller crunches, its just when we fire up a massive job
> this happens.  We've got some more hardware coming in, but it will only
> lessen the problem, not cure it.

If your crunching allows you do do so, you might want to poll the
current replication lag occasionally and pause the process if you are
lagged above some threshold of your choosing.

> So, my current thinking is if I setup a slave off of prod, lets call him
> crunchmaster and then have the existing crunch box sync off of crunchmaster
> will that insulate prod from crunch getting lagged? (as in, if crunchmaster
> is in sync, will prod be able to purge from sl_log, but crunchmaster's
> sl_logs will continue to grow until crunch is caught up?)

Dunno :-)


-- 
Stuart Bishop <stuart at stuartbishop.net>
http://www.stuartbishop.net/