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 for an example. 2016-02-13 19:11 GMT+01:00 Andrea Brancatelli <abrancate...@schema31.it>: > 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 > > > > Il 2016-02-13 17:26 Matt . ha scritto: > > 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 it writes > to it and the software connects again but the loadbalancer says, ok, > use another server now because the other one is "too busy" you might > run into trouble. > > My question is in this case, does DBmail lock the tables when it > writes to it ? otherwise I can sismple change weigth to prio, > otherwise I will let this be as I don't have these issues (yet) with > DBmail. > > Thanks! > > Matt > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org > http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
