Hi,
I am looking at the limitations of mysql cluster and one point I need more clarity is around the durability. https://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-unsupported.html "There are no durable commits on disk..."
When a transaction makes a commit on the cluster does that mean that the data is still in memory of all nodes for sometime. And later the data gets written to the disk by the asynchronous process.
So given a cluster where node group 1 has two data nodes A and B. Transaction Tx1 gets committed from the application point of view. For some reasons data nodes A and B go down before the data gets written to disk. Is it true to say that we can have a data loss on this scenario?
Thanks
I am looking at the limitations of mysql cluster and one point I need more clarity is around the durability. https://dev.mysql.com/doc/refman/5.1/en/mysql-cluster-limitations-unsupported.html "There are no durable commits on disk..."
When a transaction makes a commit on the cluster does that mean that the data is still in memory of all nodes for sometime. And later the data gets written to the disk by the asynchronous process.
So given a cluster where node group 1 has two data nodes A and B. Transaction Tx1 gets committed from the application point of view. For some reasons data nodes A and B go down before the data gets written to disk. Is it true to say that we can have a data loss on this scenario?
Thanks