Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by crypto5 on Friday November 02, 2012 @06:01PM
(#4734978)
Not exactly. Cassandra writes commit log, and if JVM will crash, cassandra will repair data from that log.
Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by dschiptsov on Saturday November 03, 2012 @04:05PM
(#4737727)
how often it fsyncs that log?
Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by crypto5 on Saturday November 03, 2012 @05:08PM
(#4737906)
It can be configured: http://wiki.apache.org/cassandra/Durability
One option is to fsync changes before telling client that operation is succeeded.
Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by dschiptsov on Sunday November 04, 2012 @03:50PM
(#4740984)
And get what benchmarks?)
Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by crypto5 on Sunday November 04, 2012 @05:50PM
(#4741385)
Benchmark will be not so good, but do you have better choice?
Re:NoSQL databases benchmark: Cassandra, HBase, MongoDB, Riak
by ajross on Friday November 02, 2012 @03:57PM
(#4734455)
The idea behind RAM-based databases is that the data is inherently redundant. If it crashes under load the rest of the cluster still has the data. I don't know HBase well at all, but clearly no one sane would argue for a "database" which held data in DRAM on a single host.
What if JVM instance crash under load? Data lose, but, see, it is not our fault - our code is OK.