couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CGS <>
Subject Re: view_duplicated_id on CouchDB 1.2
Date Wed, 18 Apr 2012 08:19:18 GMT
Hi Stephan,

If I understood your problem correctly, you don't know if you will have
enough resources to build your view, so, you will run into the same problem
even if you rebuild your view from scratch. My solution to this problem
would be to split the database in several pieces and to create views for
each of them. In such way, you will build your views in parallel and if one
(or more) will fail due to the lack of space, you won't lose everything.
The drawback of such a solution is that you will have to write a code to
combine the views when the full process is done.

To answer your direct question, to my knowledge, you cannot avoid
rebuilding your view (that is, you cannot stop and continue later building
a view). I might be wrong though and even if you were able to do that, you
would run into the same problem unless you monitor closely your disk space.

I hope this answer will help you solving your problem. If my suggestion is
not what you are looking for, please, ignore it.


On Wed, Apr 18, 2012 at 8:52 AM, Stefan Kögl <> wrote:

> Hi,
> Compaction of one of my views stopped with the following error
> {"error":"view_duplicated_id","reason":"8c40fc1a160920a958b95e8d111aabb0"}
> (full log at The view
> and underlying database have been built and compacted with CouchDB
> 1.2.
> As discussed with dch in IRC yesterday, I'm trying to fix the problem
> temporarily by making a whitespace change to one of the views in the
> group (to change its sig), upload it with another name and index it.
> After it is built, I'll copy it over the broken view. However the view
> rebuild takes a few days and I'm afraid I will run out of disk space
> in the meantime because of the growing view. Is there any other way to
> get rid of the duplicate in the view?
> Thanks,
> Stefan

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