Not exactly, transaction information is stored in disk to restore it in case
you stop a data node and restart it again.
The idea is that there are several data nodes storing replicated data and
some of them can fail as long as there are nodes available (redundancy can
be specified in the cluster parameters (noOfReplicas,...)). When the failed
node come online again it retrieves the data from the surviving nodes so the
data survives to node failures.
You can start a cluster backup from the management node to effectively write
the cluster information on disk so you can afterwards recover the cluster.
From mysql 5.1 you can use ndb engine and configure it
to store the data on
the disk instead of storing it on memory. However keys are
still required to
be stored on memory.
Summarising,
Samuel.
2007/11/15, Iñaki Baz Castillo <ibc(a)in.ilimit.es>es>:
El Thursday 15 November 2007 08:13:53 Klaus Darilion escribió:
> The basic conclusion: NDB (mysql cluster) is
the fastest engine
because
it is a
main-memory engine and has advanced locking like InnoDB.
So if the cluster fails, all the data is gone?
No experience with this, but I assume data is saved to disk periodically,
isn't?
--
Iñaki Baz Castillo
ibc(a)in.ilimit.es
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users