couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Filipe Manana (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-994) Crash after compacting large views
Date Tue, 14 Jun 2011 15:05:47 GMT


Filipe Manana updated COUCHDB-994:

    Attachment: couchdb-994-db-open-logic.patch

Stefan, try this patch instead (couchdb-994-db-open-logic.patch).

This is something I've been wanting to do for some time now, to avoid opening the databases
in one process and then pass them to another, as this goes a bit against the ref counting

This is a complement to Adam's observations, and together with previous patch (infinity timeout
for the ref counter calls), should eliminate this view compaction issue.
Adam, do you think you can give a quick look to this patch?

Thank you both

> Crash after compacting large views
> ----------------------------------
>                 Key: COUCHDB-994
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>    Affects Versions: 1.0.2
>         Environment: Centos5 64bit vm with 2CPU and 4G RAM running Erlang R14B and configured
to use the 64bit js-devel libraries.
> URL:
> Repository Root:
> Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68
> Revision: 1050680
>            Reporter: Bob Clary
>             Fix For: 1.2
>         Attachments: 2011-06-11-couchdb.log, 2011-06-13-couchdb.log, couch_errors.txt,
couch_errors_2.txt, couchdb-994-db-open-logic.patch
> The database has over 9 million records. Several of the views are relatively dense in
that they emit a key for most documents. The views are successfully created initially but
with relatively large sizes from 20 to 95G. When attempting to compact them, the server will
crash upon completion of the compaction.
> This does not occur with the released 1.0.1 version but does with the 1.0.x svn version.
I'll attach example logs. Unfortunately they are level error and may not have enough information.

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message