Actually, somehow I totally misread this; he said mysql clustering,
and I kept thinking replication.
Yeah, clustering at the moment I consider a wash; I'm not going to
bother with it, possibly even with the file-based as well. Too many
odd stipulations.
All I really need are a couple beefy boxes in failover configuration
and things like memcache to alleviate unnecessary trips to the
database.
On 10/31/05, Mark <msalists@xxxxxxx> wrote:
> > Why don't you do Mysql clustering means on the same server on
> > which apache is running you can do mysql clustering.With
> > mysql clustering if one server goes down the other is still
> > available and when the server comes back it can take the data
> > from the other mysql data node.
> >
>
> Only problem is the cluster storage engine needs to have all data in-memory
> and can't work on files (yet), so if you have a big
> database, you need tons of RAM. Someone said they will be coming out with
> file-based clustering in 5.1, but since 5.0 was just
> released last week, that might take a while...
|