Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of robert.newson@gmail.com
 designates 209.85.216.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=OZEGVu0NayjguZ+Hf91oeSYawL7YiixkSKoAllL8GgPmuaI00ffXl8zEBCLvWO57Wr
         BQBRIy9heDvDk1zOaPLm9C+b10jQSVCsEbrns6Kda1m6GzGZtRjhx63OhSFpw3xOnEIW
         p6v6Ks8X4DtFFmw6WT6kq4bP76bKTR9VUte8c=
MIME-Version: 1.0
In-Reply-To: <7CA14791-C5C3-435A-84C5-E7EB28872A09@apache.org>
References: <1200970.2551290897937827.JavaMail.jira@thor>
	<7CA14791-C5C3-435A-84C5-E7EB28872A09@apache.org>
Date: Sun, 28 Nov 2010 13:39:31 +0000
Message-ID: <AANLkTi=FnTJrMSbRw4NR3-puOHWYno2+uupU0OCRsqs9@mail.gmail.com>
Subject: Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
From: Robert Newson <robert.newson@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

+1

On Sun, Nov 28, 2010 at 12:55 PM, Jan Lehnardt <jan@apache.org> wrote:
>
> On 27 Nov 2010, at 23:45, Adam Kocoloski (JIRA) wrote:
>
>>
>> =A0 =A0 [ https://issues.apache.org/jira/browse/COUCHDB-968?page=3Dcom.a=
tlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>> Adam Kocoloski updated COUCHDB-968:
>> -----------------------------------
>>
>> =A0 =A0Priority: Blocker =A0(was: Major)
>
> Should we hold 1.0.2 for this?
>
> Cheers
> Jan
> --
>
>>
>> Bob, in tisba's case the duplicates had the same revision. =A0Is that al=
so true in your case? =A0And you only see these duplicates after compaction=
?
>>
>>> Duplicated IDs in _all_docs
>>> ---------------------------
>>>
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Key: COUCHDB-968
>>> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0URL: https://issues.apache.org/jira/brow=
se/COUCHDB-968
>>> =A0 =A0 =A0 =A0 =A0 =A0Project: CouchDB
>>> =A0 =A0 =A0 =A0 Issue Type: Bug
>>> =A0 =A0 =A0 =A0 Components: Database Core
>>> =A0 Affects Versions: 1.0, 1.0.1, 1.0.2
>>> =A0 =A0 =A0 =A0Environment: Ubuntu 10.04.
>>> =A0 =A0 =A0 =A0 =A0 Reporter: Sebastian Cohnen
>>> =A0 =A0 =A0 =A0 =A0 Priority: Blocker
>>>
>>> We have a database, which is causing serious trouble with compaction an=
d replication (huge memory and cpu usage, often causing couchdb to crash b/=
c all system memory is exhausted). Yesterday we discovered that db/_all_doc=
s is reporting duplicated IDs (see [1]). Until a few minutes ago we thought=
 that there are only few duplicates but today I took a closer look and I fo=
und 10 IDs which sum up to a total of 922 duplicates. Some of them have onl=
y 1 duplicate, others have hundreds.
>>> Some facts about the database in question:
>>> * ~13k documents, with 3-5k revs each
>>> * all duplicated documents are in conflict (with 1 up to 14 conflicts)
>>> * compaction is run on a daily bases
>>> * several thousands updates per hour
>>> * multi-master setup with pull replication from each other
>>> * delayed_commits=3Dfalse on all nodes
>>> * used couchdb versions 1.0.0 and 1.0.x (*)
>>> Unfortunately the database's contents are confidential and I'm not allo=
wed to publish it.
>>> [1]: Part of http://localhost:5984/DBNAME/_all_docs
>>> ...
>>> {"id":"9997","key":"9997","value":{"rev":"6096-603c68c1fa90ac3f56cf5377=
1337ac9f"}},
>>> {"id":"9999","key":"9999","value":{"rev":"6097-3c873ccf6875ff3c4e2c6fa2=
64c6a180"}},
>>> {"id":"9999","key":"9999","value":{"rev":"6097-3c873ccf6875ff3c4e2c6fa2=
64c6a180"}},
>>> ...
>>> [*]
>>> There were two (old) servers (1.0.0) in production (already having the =
replication and compaction issues). Then two servers (1.0.x) were added and=
 replication was set up to bring them in sync with the old production serve=
rs since the two new servers were meant to replace the old ones (to update =
node.js application code among other things).
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>
>