ALL COVERED TOPICS

NoSQLBenchmarksNoSQL use casesNoSQL VideosNoSQL Hybrid SolutionsNoSQL PresentationsBig DataHadoopMapReducePigHiveFlume OozieSqoopHDFSZooKeeperCascadingCascalog BigTableCassandraHBaseHypertableCouchbaseCouchDBMongoDBOrientDBRavenDBJackrabbitTerrastoreAmazon DynamoDBRedisRiakProject VoldemortTokyo CabinetKyoto CabinetmemcachedAmazon SimpleDBDatomicMemcacheDBM/DBGT.MAmazon DynamoDynomiteMnesiaYahoo! PNUTS/SherpaNeo4jInfoGridSones GraphDBInfiniteGraphAllegroGraphMarkLogicClustrixCouchDB Case StudiesMongoDB Case StudiesNoSQL at AdobeNoSQL at FacebookNoSQL at Twitter

NAVIGATE MAIN CATEGORIES

Close

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

via: http://couchdb.apache.org/notice/1.0.1.html