Hi Bhanu! As long as you follow the official recommendation to set `delayed_commits` to `true` (see the `couchdb` section in the configuration), CouchDB guarantees that a success for a write operation is only indicated if it has received a ok return code from a `fsync` call at the end of the particular write operation.
Please note that (unfortunately) `delayed_commits` currently still defaults to `true`, so you need to change it to `false` in order to have that guarantee. Regarding the `delayed_commits` configuration, see here: http://docs.couchdb.org/en/latest/config/couchdb.html?highlight=delayed_commits#couchdb/delayed_commits Cheers, Klaus On 07/10/2014 09:07 AM, Bhanu wrote: > Hi, > > I am interested in knowing what level of reliability and durability > guarantees CouchDB provides? Are there any corner cases in which I can lose > my data? Are there any cases where I receive an acknowledgement and still > data is lost? > > 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-tp7593186.html > Sent from the CouchDB Development mailing list archive at Nabble.com. >
signature.asc
Description: OpenPGP digital signature
