ALL COVERED TOPICS

NoSQL Benchmarks NoSQL use cases NoSQL Videos NoSQL Hybrid Solutions NoSQL Presentations Big Data Hadoop MapReduce Pig Hive Flume Oozie Sqoop HDFS ZooKeeper Cascading Cascalog BigTable Cassandra HBase Hypertable Couchbase CouchDB MongoDB OrientDB RavenDB Jackrabbit Terrastore Amazon DynamoDB Redis Riak Project Voldemort Tokyo Cabinet Kyoto Cabinet memcached Amazon SimpleDB Datomic MemcacheDB M/DB GT.M Amazon Dynamo Dynomite Mnesia Yahoo! PNUTS/Sherpa Neo4j InfoGrid Sones GraphDB InfiniteGraph AllegroGraph MarkLogic Clustrix CouchDB Case Studies MongoDB Case Studies NoSQL at Adobe NoSQL at Facebook NoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

MongoDB, Data Durability and Improvements coming in 1.8

Mathias Meyer:

My point here is simple: even when killed using the KILL signal, a database should not be unrecoverable. It simply shouldn’t be allowed to happen. You can blame the guy all you want for using kill -9, but consider the fact that it’s the process equivalent of a server or even just the database process crashing hard. Which happens, believe it or not.

[…] And this is what horrifies me, people seem to accept that this is simply one of MongoDB’s trade-offs, and that it should just be considered normal. They shouldn’t

That is no different than what I’ve said.

Original title and link: MongoDB, Data Durability and Improvements coming in 1.8 (NoSQL databases © myNoSQL)

via: http://www.paperplanes.de/2011/1/10/mongodb_and_data_durability.html