couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Newson (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-791) Changes not written if server shutdown during delayed_commits period
Date Thu, 10 Jun 2010 13:58:22 GMT

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

Robert Newson commented on COUCHDB-791:
---------------------------------------


Just my opinion but I think this is the correct behavior. Keeping to the "crash only" shutdown
behavior is desirable, as soon as couchdb starts caring about clean vs. unclean shutdown,
we'll introduce complexity best avoided.


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


Mime
View raw message