Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of dave@muse.net.nz designates
 209.85.212.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPinO9e9z4bndagMFrgLk3tUFkSUM2xBiyCq=KQim-63s-Xs+w@mail.gmail.com>
References: 
 <CAPinO9e9z4bndagMFrgLk3tUFkSUM2xBiyCq=KQim-63s-Xs+w@mail.gmail.com>
Date: Wed, 18 Apr 2012 10:48:00 +0200
Message-ID: 
 <CAHZBNKb7iLES2cvJuc-fTFTMxPdkhhF3H-iZ19HDXxO1usM-qQ@mail.gmail.com>
Subject: Re: view_duplicated_id on CouchDB 1.2
From: Dave Cottlehuber <dave@muse.net.nz>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 18 April 2012 08:52, Stefan K=F6gl <koeglstefan@gmail.com> wrote:
> Hi,
>
> Compaction of one of my views stopped with the following error
> {"error":"view_duplicated_id","reason":"8c40fc1a160920a958b95e8d111aabb0"=
}
> (full log at https://friendpaste.com/6n5skP4QKfAGZNGMcYPHAR). 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

Hi Stefan,

There's some background reading[1],[2],[3]  where the issue of
duplicate docs and revision limits is discussed in some depth,
although these specific issues were resolved prior to 1.2.0 & I can't
replicate those specific issues again in 1.2.0.

[1]: https://issues.apache.org/jira/browse/COUCHDB-999
[2]: https://issues.apache.org/jira/browse/COUCHDB-968
[3]: https://issues.apache.org/jira/browse/COUCHDB-888

BTW what is the rev_limit on that db, any chance of having gone over
it for some docs, and subsequently replicated between nodes?
$COUCH/db/_revs_limit to query the per-db limit.

A+
Dave