couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adam Kocoloski (JIRA)" <>
Subject [jira] [Commented] (COUCHDB-1769) Duplicates in View indexes
Date Tue, 28 May 2013 20:01:21 GMT


Adam Kocoloski commented on COUCHDB-1769:

Hmm, that's what I get for doing this from memory ... it seems like we do optimize away the
entries to the btree in the case where a doc doesn't emit anything.

The other weird bit is that I thought we had fixed up couch_btree to disallow duplicate keys
altogether by now.  Need to dig in on this a bit more.
> Duplicates in View indexes
> --------------------------
>                 Key: COUCHDB-1769
>                 URL:
>             Project: CouchDB
>          Issue Type: Bug
>          Components: JavaScript View Server
>    Affects Versions: 1.3
>            Reporter: Stefan Kögl
>         Attachments: duplicate.log
> The compaction of a view (created with CouchDB 1.3) failed due to view_duplicate_id.
The database to which the view belongs was created with 1.2.x but compacted (with the 0-byte-compact-file
trick) with 1.3.
> A full log of the failed compaction can be found at
> I experienced the same behaviour already with previous versions but assumed it might
be gone with 1.3, but this seems not to be the case. 
> When such duplicates happen (and appear during compaction), they seem to be at the beginning
of the view index. The view in question has the following _info:
> {noformat}
> {"name":"listeners","view_index":{"signature":"854a8065b438b3e53fcdbbe0a79a8e80","language":"javascript","disk_size":2679632207,"data_size":1026614011,"update_seq":58353111,"purge_seq":0,"updater_running":false,"compact_running":false,"waiting_commit":false,"waiting_clients":0}}
> {noformat}
> Compaction stopped with a 39M large .compact.view file.
> Also the problem seems to happen only one some machines.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message