[
https://issues.apache.org/jira/browse/COUCHDB-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878642#action_12878642
]
Damien Katz commented on COUCHDB-791:
-------------------------------------
Neither of those options is guaranteed to fully write to disk. This just isn't
how CouchDB is designed. It's crash-only, never has a shutdown phase, and if it
detects an internal error, it immediately will crash.
If you need things to be guaranteed committed, then don't use delayed commits.
Otherwise you are always at risk of losing the most recent updates.
> Changes not written if server shutdown during delayed_commits period
> --------------------------------------------------------------------
>
> Key: COUCHDB-791
> URL: https://issues.apache.org/jira/browse/COUCHDB-791
> Project: CouchDB
> Issue Type: Bug
> Affects Versions: 0.11.1
> Environment: Linux (Ubuntu 10.04)
> Reporter: Matt Goodall
>
> If the couchdb server is shutdown (couchdb -d, Ctrl+C at the console, etc)
> during the delayed commits period then buffered updates are lost.
> Simple script to demonstrate the problem is:
> db=http://localhost:5984/scratch
> curl $db -X DELETE
> curl $db -X PUT
> curl $db -X POST -d '{}'
> /path/to/couchdb/bin/couchdb -d
> When couchdb is started again the database is empty.
> Affects 0.11.x and trunk branches.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
