On Tuesday 03 August 2004 01:11 pm, Jon Drukman wrote:
> We were having terrible problems with a master/slave setup. The master
> does a huge amount of writes, and the slave simply started lagging
> behind, despite both machines being identical hardware-wise. This made
> the application basically
> From: David Griffiths [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, August 03, 2004 1:04 PM
> Subject: Re: Replication + InnoDB = badness
>
> Could it be a network bandwidth issue? Remember, all that
> data needs to
> be transmitted across to the slave. If you are on a
Could it be a network bandwidth issue? Remember, all that data needs to
be transmitted across to the slave. If you are on a 10-megabit network,
it could be the cause. Remember, Ethernet is not exactly an efficient
protocol, and efficiency drops as network traffic increases.
A second machine mig
> > Also even after we re-converted all the slave's Inno tables back to
> > MyISAM it *still* lagged out. Only after I disabled the
> Inno engine
> > entirely did the problem abate.
> >
> > Any ideas why? Does InnoDB use resources even if there are no
> > active tables using the engine?
>
>
On Tue, Aug 03, 2004 at 11:11:52AM -0700, Jon Drukman wrote:
>
> We were having terrible problems with a master/slave setup. The
> master does a huge amount of writes, and the slave simply started
> lagging behind, despite both machines being identical hardware-wise.
> This made the application ba
