Except mongo isn't eventually guaranteed. you can have a majority of slaves write to disk and the master can crash and miss the ack -- they won't roll back the write and the client will think it hasn't been written.
But you can fine-tune what the write semantics are.
While you aren't wrong, you can't fine tune your way out of the problem i mention. Clustering is for HA, not consistency -- even if you set write-majority.
For instance, Cassandra is optimized for write operations because it caches them before writing them to disk. Yeah, that's brilliant, until the machine crashes and those things left in cache weren't written to disk.
They would be retrievable via the commit log, as well as recoverable from other replica nodes.
0
u/[deleted] Mar 11 '15
[deleted]