couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] [Updated] (COUCHDB-994) Crash after compacting large views
Date Fri, 05 Aug 2011 19:45:28 GMT


Adam Kocoloski updated COUCHDB-994:

    Attachment: 0001-Write-header-before-handing-over-compacted-group.patch

Here's a patch to address issue #1.  It ensures that the compacted view group has a valid
header before handing it over to the couch_view_group process.  This means that the index
will not be reset if the server crashes after the file has been renamed but before the next
delayed_commit message arrives.

It does not address the possibility of using a .compact view index if the main index file
has been deleted, which could happen if the server crashes in between the delete and the rename.

> 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.1.1, 1.2
>         Attachments: 0001-Write-header-before-handing-over-compacted-group.patch, 2011-06-11-couchdb.log,
2011-06-13-couchdb.log, 2011-06-15-2-couchdb.log, 2011-06-15-couchdb.log, 2011-06-16-couchdb.log,
couch_errors.txt, couch_errors_2.txt, couchdb-994-db-open-logic-11x.patch, 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