[rt-users] Failover/Loadbalance

[Matthew Watson]

Mysql's clustering probably wouldn't be much good for RT, last I heard
their clustering solution required your entire dataset to be loaded into
RAM, so unless you have a very small database (or A LOT of RAM) this
probably wont work.

Mysql also offers replication, using a single master and many slaves, I
believe this would however require a bit of work in RT3, as it would
need separate database handles for reads and writes I believe.

Matt.


> -----Original Message-----
> From: rt-users-bounces at lists.bestpractical.com [mailto:rt-users-
> bounces at lists.bestpractical.com] On Behalf Of Asif Iqbal
> Sent: Tuesday, January 25, 2005 12:42 AM
> To: rt-users at lists.bestpractical.com
> Subject: [rt-users] Failover/Loadbalance
> 
> Hi All
> 
> I am looking for a solution of RT3.2.2 with Mysql 4.0.13 (or higher
that
> RT recommends) under Solaris 8 to setup as
Loadbalance/failover/cluster
> through the WAN.
> I know mysql 4.1.x supports clustering. Not sure if Apache does
anything
> like that or not. But just to stick with RT's recommendation I think
> mysql 4.1 is not recommended yet.
> 
> Has anyone done any setup similar to this?
> 
> Any feedback is appreciated.
> 
> Thanks
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
> "...it said: Install Windows XP or better...so I installed Solaris..."
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
> 
> RT Administrator and Developer training is coming to your town soon!
> (Boston, San Francisco, Austin, Sydney) Contact
training at bestpractical.com
> for details.
> 
> Be sure to check out the RT Wiki at http://wiki.bestpractical.com

This email and any files transmitted with it are confidential and intended solely for the 
use of the individual or entity to whom they are addressed. Please notify the sender 
immediately by email if you have received this email by mistake and delete this email 
from your system. Please note that any views or opinions presented in this email are solely
 those of the author and do not necessarily represent those of the organisation. 
Finally, the recipient should check this email and any attachments for the presence of 
viruses. The organisation accepts no liability for any damage caused by any virus 
transmitted by this email.