couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: Faster updates, optional ACID
Date Mon, 05 Jan 2009 19:54:46 GMT

On 5 Jan 2009, at 18:54, Damien Katz wrote:
> The last remaining work item is db server crash detection, so that  
> clients can detect when a server has crashed and potentially lost  
> updates. This is pretty simple, each db server just needs a unique  
> ID generated at it's startup. Client retrieve this value at the  
> beginning of the writes and then checks that the value is the same  
> once down a flushed to disk. If not, we know we maybe have lost some  
> updates and we redo the replication from the last known good commit.

We should document that pattern for clients that use CouchDB
and put in data without replication. Their writes might also not
go in.

> Right now the default is to delay the commits, because I think that  
> will be the most common use case but I'm really not sure. I  
> definitely want the commits delayed for the test suite, to keep  
> things running fast.



View raw message