<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7650.28">
<TITLE>AW: Re: [rt-users] RT and mysql replication</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>Hi,<BR>
Just to pick up this discussion, this palnned scenario would be very, very clever, should be added to the rt4 wish list.<BR>
<BR>
Torsten.<BR>
<BR>
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.<BR>
<BR>
-----Original Message-----<BR>
From: rt-users-bounces@lists.bestpractical.com <rt-users-bounces@lists.bestpractical.com><BR>
To: rt-users@lists.bestpractical.com <rt-users@lists.bestpractical.com><BR>
Sent: Fri May 04 16:27:05 2007<BR>
Subject: Re: [rt-users] RT and mysql replication<BR>
<BR>
Alle 15:39, venerdì 4 maggio 2007, Bob Goldstein ha scritto:<BR>
<BR>
<BR>
> I don't believe this is an RT question. Mysql supports replication,<BR>
> for sure at 4.x, and supports clusters at 5.x.<BR>
<BR>
As far as in a replication cluster scenario applications must perform insert<BR>
and updates only onto the master db server and can perform select onto an<BR>
arbitrary slave server of the cluster, this will be an RT question: code must<BR>
be patched to follow this behaviour.<BR>
<BR>
<BR>
> Do the needful at the mysql level, RT doesn't care.<BR>
<BR>
RT doesn't care because it use only one cluster server: the master server.<BR>
<BR>
We're using RT in an heavy duty environment (about 1500/1600 tickets per day),<BR>
with about 90 different CRM operators, and using a single mysql server is not<BR>
a good deal: if RT can split searches onto some slaves db servers (4/5 slave<BR>
server) it can improve all operativeness.<BR>
<BR>
<BR>
<BR>
--<BR>
Luca Villani Mobile Team, Dada S.p.A.<BR>
Tel: +39 055 2267220 Mob: +39 335 8753086<BR>
ICQ: 76272621 Skype: luca.villani<BR>
GPG key fingerprint: 7FC9 E2FE 0BEE 9DF8 1719 8761 1B79 82CC F0B5 B7CF<BR>
_______________________________________________<BR>
<A HREF="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</A><BR>
<BR>
Community help: <A HREF="http://wiki.bestpractical.com">http://wiki.bestpractical.com</A><BR>
Commercial support: sales@bestpractical.com<BR>
<BR>
<BR>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.<BR>
Buy a copy at <A HREF="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</A><BR>
</FONT>
</P>
</BODY>
</HTML>