Others may have had more success with this but from experience of MySQL in multi-master setups I would avoid this entirely.
A common setup is using DRDB to provide a master/slave: Management 1 (MySQL Master) w/ virtual IP Management 2 (MySQL Slave) HA IP Address (for agents/services requiring DB write) which is assigned to the master (using Pacemaker). You can then send web management client to the HA IP Address as well. It may be worth considering if you need load balancing, depending on your setup - what loads are you experiencing? Marty On Tue, Nov 5, 2013 at 5:13 PM, Adrian Lewis <adr...@alsiconsulting.co.uk>wrote: > Hi All, > > > > Just wondering if anyone is using a MySQL multi-master configuration with > auto_increment_offset (e.g.10) and auto_increment_increment (1 for server > 1, 2 for server 2 etc)? Does it work? Does anyone know a reason why it > doesn’t or wouldn’t work? Is there anything from an application point of > view that could/would trip up CS if auto_increment values are set as more > than 1? > > > > Not planning on deploying multimaster just yet but if I at least start with > an auto_increment of 10, I’d have the option of adding a second master > later and being able to load-balance more effectively. > > > > Thanks in advance, > > > > Adrian >
