With delayed commits to false, my understanding is that every write will be immediately flushed to disk which may affect the overall performance of couchdb. Is there any way to get durability guarantee with delayed commits set to true?
Does couchdb not use any journalling/write-ahead logging like mongodb does -- so that journal files could be written more frequently than the actual data file? Since CouchDB is AP with eventual consistency, I believe it suffers from same mongodb issues mentioned here -- https://groups.google.com/forum/#!topic/mongodb-user/SDY82VKzif0 Is there any case where couchdb will lose write though the write is successfully acknowledged to client? Can we say that if delayed_commits is set to true, then CouchDB might lose data? When will client receive acknowledgement in this case (delayed_commits = true)? After the flushing or immediately? Thanks, Bhanu -- View this message in context: http://couchdb-development.1959287.n2.nabble.com/What-are-the-cases-in-which-we-can-see-data-loss-with-CouchDB-tp7593186p7593325.html Sent from the CouchDB Development mailing list archive at Nabble.com.
