MySQL NDB Cluster uses row level locks instead of a single shared
commit lock in order to prevent inconsistency in simultaneous
distributed transactions. This gives NDB a great advantage over
all other MySQL clustering solutions and is one reason behind
cluster’s unmatched ability to scale both reads and
writes.
NDB is a transactional data store. The lowest and only isolation
level available in NDB is Read Committed. There are no dirty
reads in NDB and only committed rows can be read by other
transactions.
All write transactions in NDB will result in exclusive row locks
of all individual rows changed during the transaction. Any other
transaction is allowed to read any committed row independent of
their lock status. Reads are lock-free reads.
The great advantage is that committed reads in NDB never block
during writes to the same data and always the latest committed
changes are read. A select doesn't block concurrent …
Showing entries 1 to 1
Nov
15
2018
Showing entries 1 to 1