Hi,
Just to pick up this discussion, this palnned scenario would be very, very clever, should be added to the rt4 wish list.
Torsten.
Btw: on on mysql cluster won’t help if you have on on very big environment, the replica architecture would be the best way i think.From: rt-users-bounces@lists.bestpractical.com rt-users-bounces@lists.bestpractical.com
To: rt-users@lists.bestpractical.com rt-users@lists.bestpractical.com
Sent: Fri May 04 16:27:05 2007
Subject: Re: [rt-users] RT and mysql replication
Alle 15:39, venerdì 4 maggio 2007, Bob Goldstein ha scritto:
I don’t believe this is an RT question. Mysql supports replication,
for sure at 4.x, and supports clusters at 5.x.
As far as in a replication cluster scenario applications must perform insert
and updates only onto the master db server and can perform select onto an
arbitrary slave server of the cluster, this will be an RT question: code must
be patched to follow this behaviour.
Do the needful at the mysql level, RT doesn’t care.
RT doesn’t care because it use only one cluster server: the master server.
We’re using RT in an heavy duty environment (about 1500/1600 tickets per day),
with about 90 different CRM operators, and using a single mysql server is not
a good deal: if RT can split searches onto some slaves db servers (4/5 slave
server) it can improve all operativeness.
Luca Villani Mobile Team, Dada S.p.A.
Tel: +39 055 2267220 Mob: +39 335 8753086
ICQ: 76272621 Skype: luca.villani
GPG key fingerprint: 7FC9 E2FE 0BEE 9DF8 1719 8761 1B79 82CC F0B5 B7CF
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com
Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com