[
https://issues.apache.org/jira/browse/COUCHDB-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12878589#action_12878589
]
Sebastian Cohnen commented on COUCHDB-791:
------------------------------------------
@chris: when couchdb -d calls /_ensure_full_commit before it kills the pid, how
to avoid on high traffic use cases that there are no more inserts/updates while
or after _ensure_full_commit is done and BEFORE the couchdb process is killed?
I think if there is such a mechanism, it should work reliably in all cases.
Otherwise the current approach of killing the process and hope the best is
already sufficient. (for scheduled maintenance there are ways to gracefully
shut down couch, like blocking further incoming requests and wait until all
updates are finished. but you have to hack it yourself at the moment)
> 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.
