You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Chris Anderson (JIRA)" <ji...@apache.org> on 2010/06/10 15:55:13 UTC

[jira] Commented: (COUCHDB-791) Changes not written if server shutdown during delayed_commits period

    [ https://issues.apache.org/jira/browse/COUCHDB-791?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877415#action_12877415 ] 

Chris Anderson commented on COUCHDB-791:
----------------------------------------

This is the expected behavior. To avoid this, turn delayed_commits off.

In my experience CouchDB has higher throughput under concurrent load without delayed_commits, so they are really only a performance aid in the single-user or naive-benchmark use case.

> 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.