Quoting Ira Abramov, from the post of Mon, 14 Feb:
> 
> 4. I install a MySQL cluster, which I've no experiance in yet. their
> website says it's a "share nothing cluster" in one place, but then talks
> about a common storage node in another. Either way it's not pre-packaged

OK, I read a bit more about it. seems like the situation is:

http://www.linux-mag.com/2004-10/mysql_01.html

I can have any number of backend storage nodes, to use them I ask for an
NDBCluster storage engine for a table (rather than InnoDB or MyISAM),
and the DB is kept in the storage nodes' RAM with a certain hash and
always on two nodes (if I get it right, the total sum of
available-to-MySQL RAM on all the nodes musat be at least twice the
total sum of the databases (or table spaces) I am serving).

The article mentions another restriction or two, namely full text search
is not available (probably not a problem for this project) and that
although I can place two or more API nodes in front of the NDB cluster,
I must make sure that the writes come only through one of them. i.e. no
shared write locking I guess? At least it means that both API nodes I'll
use are sorta symetric, and no daemons need to be allerted when I start
doing writes to the other node instead. I just need to be aware that
writes must never be to both nodes (at least not on the same table).

Did I get it right?


-- 
Walking on sunshine
Ira Abramov
http://ira.abramov.org/email/

=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]

Reply via email to