Hi,
I'm reviewing how software is acting on loadbalaced MySQL cluster in a
MultiMaster replication.
I see some software having issues to a frontend that is balanced on
weight so if you put a lot of data to the frontend of the cluster, all
nodes are written and if the software locks the table when
InnoDB/MySQL locking is row level, not table level.
It's highly improbable you'll have any problem like that.
---
Andrea Brancatelli
Schema31 S.p.a.
Responsabile IT
ROMA - BO - FI - PA
ITALY
Tel: +39. 06.98.358.472
Cell: +39 331.2488468
Fax: +39. 055.71.880.466
Società del Gruppo SC31 ITALIA
Hi,
Thanks, yes I'm checking out the various software I use.
The issue might be that updated status rows are locked, for an example
when 2 messages are stores @ the same time on 2 different sql servers
and need to update another reference row as well.
I see this on logging software happening too
If a two messages arrive at the same time on two different sql server
they are written in two different rows. There's no racing condition.
---
Andrea Brancatelli
Schema31 S.p.a.
Responsabile IT
ROMA - BO - FI - PA
ITALY
Tel: +39. 06.98.358.472
Cell: +39 331.2488468
Fax: +39. 055.71.880.466
Soc