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



CouchDB 1.0: Critical Bug Found, Fix Available

Simply put, you may lose your data. Fortunately there’s a very detailed solution for it:

If you are using CouchDB 1.0.0 and have the default setting for ‘delayed_commits’ (true) then you are affected by this data loss bug.


For current users, these instructions will ensure your data is safe. First: do not restart your CouchDB!

The bug doesn’t affect previous CouchDB releases.

CouchDB 1.0: Critical Bug Found, Fix Available originally posted on the NoSQL blog: myNoSQL