couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Steven Hazel <...@saucelabs.com>
Subject Re: An asynchronous write bug in CouchDB 0.9?
Date Mon, 27 Apr 2009 16:40:16 GMT
I think we do have a lot of active databases -- we have a view that is run
frequently against each of our 137 databases.

- Steve

On Mon, Apr 27, 2009 at 6:20 AM, Damien Katz <damien@apache.org> wrote:

> It looks like the db server instance is being restarted before it commits
> the header, but it's odd you aren't seeing any errors on the console. If
> it's a crash it should dump an error to the console.
>
> One thing that occurs to me, do you have a lot of active databases (> 100)
> ? I think it's possible when you hit the max dbs open, CouchDB will shutdown
> an idle instance with pending deferred commit, which is a bug.
>
> -Damien
>
>
>
> On Apr 27, 2009, at 12:52 AM, Steven Hazel wrote:
>
>  Hi,
>>
>> Last week we discovered that records in one of our CouchDB databases were
>> occasionally being reverted to the previous revision. We believe this is
>> due
>> to a bug in CouchDB 0.9 related to asynchronous writes.  Turning off
>> asynchronous writes with the X-Couch-Full-Commit header fixes the problem
>> for us.  I've written up the problem in more detail here:
>> http://saucelabs.com/couch-bug.html
>>
>> We haven't yet reproduced this problem outside our production environment,
>> but can trigger it there on-demand.  Although we have a work-around that
>> solves the immediate problem for us, we're happy to help out in tracking
>> down the underlying issue.  Any advice on how to proceed would be
>> appreciated.
>>
>> --
>> Steven Hazel
>> Sauce Labs
>> Cofounder and Director, Development
>> http://twitter.com/sahazel
>>
>
>


-- 
Steven Hazel
Sauce Labs
Cofounder and Director, Development
http://twitter.com/sahazel

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message