couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Randall Leeds (JIRA)" <>
Subject [jira] Commented: (COUCHDB-791) Changes not written if server shutdown during delayed_commits period
Date Mon, 14 Jun 2010 18:07:14 GMT


Randall Leeds commented on COUCHDB-791:

I just had an idea I mentioned in IRC, and I think I like it.
How about just throwing a message into the startup console and into futon a la "Admin Party!"
advising people to turn it off when they plan to put things in production? Might be a little
confusing. There's the chance that people might accuse CouchDB of being sneaky to improve
benchmarks, but really, that's kinda what delayed_commits is doing. A big message about it,
however, is far from sneaky.

> Changes not written if server shutdown during delayed_commits period
> --------------------------------------------------------------------
>                 Key: COUCHDB-791
>                 URL:
>             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.

View raw message