[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: Documentation volunteer (was: Cluster replication: multiple masters)

=> On Wed, 16 Oct 2002 09:02:47 +0200, Markus Storm <markus.storm@mediaways.net> said:

> Howard Chu wrote:

>> It is not straightforward to enforce the single-writer usage though; i.e.,
>> there's no simple way to ensure that clients only write to the currently
>> selected write server.

> We have two IP on the load balancer, one for reading and the other one for
> writing. The reader one does round-robin but the writer one implements
> fail-over, i.e. the second server is only ever used if the first one is
> down.  Works fine (and hey - we're a large ISP and I guess we would be broke
> by now if it didn't).

Are your back-end servers deployed in private-IP space?  I can't come up with
another straightforward way to ensure that people don't somehow connect
directly to the back-end server and write to the wrong box.  If you do that,
though, at least you'll be limited to busted configurations within your

I don't know, but I think that's the 'ensure only write to currently selected'
problem Howard alludes to.

- Allen S. Rout