Marcus, I agree with you too, but have cases you can do it.
Best wishes,
--
Wagner Bianchi
2011/9/21 Marcus Bointon <marcus@stripped>
> On 21 Sep 2011, at 20:39, Wagner Bianchi wrote:
>
> > A good solution could be to use a MASTER <=> MASTER topology, using MySQL
> > 5.1 or 5.5, in order to split writes between servers, operation will
> > decrease a little more your workload.
>
> I really wouldn't do that. Writing to both masters will not gain you any
> performance and asks for all kinds of split-brain trouble. I've been there,
> it's not pretty. If you manage your masters with MMM, you won't be able to
> do it anyway as it sets passive masters to read-only.
>
> It's been said many times - MySQL replication is NOT a scaling solution.
> MySQL Cluster and sharding are scaling solutions, but they are unrelated to
> replication.
>
> Marcus
> --
> Marcus Bointon
> Synchromedia Limited: Creators of http://www.smartmessages.net/
> UK resellers of info@hand CRM solutions
> marcus@stripped | http://www.synchromedia.co.uk/
>
>
>
