On Wed, Feb 02, 2005 at 01:46:22PM -0700, Nick Pavlica wrote:
MySql 4.1 has been the production release since 4.1.7 and are
currently at the 4.1.9 release. You could look into the seperate
MySql Cluster product, but it is around $5k per cpu last time I
checked.
Uh --- MySQL Cluster is a
Uh --- MySQL Cluster is a standard part of 4.1.9. You just have to
install the mysql41-server port WITH_NDB=yes, which gets you a bunch
of extra executables, mostly in /usr/local/libexec, including ndb_mgmd
and ndbd. See: http://dev.mysql.com/doc/mysql/en/ndbcluster.html
Yes it's part of
--- Technical Director [EMAIL PROTECTED] wrote:
Drumslayer,
I am part of a team running MySQL 4.1.X on 5
machines in a replication
setup. Our first way to help manage load is the use
of useful rules in
our connection classes to direct Writes to our big
server with fast I/O
and memory
Drumslayer,
The only problem with this is that 4.1 is stil
considered Beta (not yet ready for production). I
see little chance in convincing managment to utilize
something beta for something so important. :(
Forgive me for being possibly naive but from what I understand 4.1.X moved
off of
All,
MySql 4.1 has been the production release since 4.1.7 and are
currently at the 4.1.9 release. You could look into the seperate
MySql Cluster product, but it is around $5k per cpu last time I
checked.
--Nick
On Wed, 2 Feb 2005 13:28:22 -0700 (MST), Technical Director
[EMAIL PROTECTED]
--- Technical Director
[EMAIL PROTECTED] wrote:
Drumslayer,
The only problem with this is that 4.1 is stil
considered Beta (not yet ready for production).
I
see little chance in convincing managment to
utilize
something beta for something so important. :(
Forgive me for being
Hi
I have been running a fairly heavy duty server for
MySQL on FreeBSD but its starting to peak. I would
like to know what others have done as far as using a
load balancing solution for MySQL or their success
with replication.
Also has anyone done a 64 bit build of MySQL on
FreeBSD successfully?
Drumslayer,
I am part of a team running MySQL 4.1.X on 5 machines in a replication
setup. Our first way to help manage load is the use of useful rules in
our connection classes to direct Writes to our big server with fast I/O
and memory and directing Rreads to our slower I/O less RAM slaves
