couchdb-dev mailing list archives

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


Robert Newson commented on COUCHDB-791:

Losing data that had reached the disk would, of course, be a scandal, but that's not the case

CouchDB does not 'shutdown', you just terminate the process. I think it's an important design
choice but clearly its consequences aren't spelled out clearly enough.

I'm familiar with other systems that distinguish 'clean' from 'dirty' shutdowns and the complexity
that brings is considerable. Worse, developers and users come to depend on it, meaning that
dirty shutdowns are rarely tested, which then leads to genuine data loss.

Since this is a closed ticket, perhaps a new @dev thread is appropriate.

> 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