[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Comment: was deleted
(was: Adam,
Thank you!
Rachel)
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1, 0.10.2, 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: any
Reporter: Sebastian Cohnen
Assignee: Adam Kocoloski
Priority: Blocker
Fix For: 0.11.3, 1.0.2, 1.1
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Fix Version/s: 0.11.3
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1, 0.10.2, 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: any
Reporter: Sebastian Cohnen
Assignee: Adam Kocoloski
Priority: Blocker
Fix For: 0.11.3, 1.0.2, 1.1
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Fix Version/s: 1.1
1.0.2
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1, 0.10.2, 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: any
Reporter: Sebastian Cohnen
Priority: Blocker
Fix For: 1.0.2, 1.1
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Environment: any (was: Ubuntu 10.04.)
Skill Level: Committers Level (Medium to Hard)
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1, 0.10.2, 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: any
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On 27 Nov 2010, at 23:45, Adam Kocoloski (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Priority: Blocker (was: Major)
Should we hold 1.0.2 for this?
Cheers
Jan
--
Bob, in tisba's case the duplicates had the same revision. Is that also true
in your case? And you only see these duplicates after compaction?
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs
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
found 10 IDs which sum up to a total of 922 duplicates. Some of them have
only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed
to publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
+1
On Sun, Nov 28, 2010 at 12:55 PM, Jan Lehnardt j...@apache.org wrote:
On 27 Nov 2010, at 23:45, Adam Kocoloski (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Priority: Blocker (was: Major)
Should we hold 1.0.2 for this?
Cheers
Jan
--
Bob, in tisba's case the duplicates had the same revision. Is that also
true in your case? And you only see these duplicates after compaction?
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs
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
found 10 IDs which sum up to a total of 922 duplicates. Some of them have
only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed
to publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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
servers 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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
+1
On 28.11.2010, at 13:55, Jan Lehnardt wrote:
On 27 Nov 2010, at 23:45, Adam Kocoloski (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Priority: Blocker (was: Major)
Should we hold 1.0.2 for this?
Cheers
Jan
--
Bob, in tisba's case the duplicates had the same revision. Is that also
true in your case? And you only see these duplicates after compaction?
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs
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
found 10 IDs which sum up to a total of 922 duplicates. Some of them have
only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed
to publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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
servers 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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
+1 On Sun, 2010-11-28 at 13:55 +0100, Jan Lehnardt wrote: On 27 Nov 2010, at 23:45, Adam Kocoloski (JIRA) wrote: [ https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Adam Kocoloski updated COUCHDB-968: --- Priority: Blocker (was: Major) Should we hold 1.0.2 for this? Cheers Jan
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson updated COUCHDB-968:
--
Affects Version/s: 0.11.1
0.11.2
Confirmed sighting in 0.11.1 and 0.11.2
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson updated COUCHDB-968:
--
Affects Version/s: 0.10.1
0.10.2
Confirmed sightings in 0.10.1 and 0.10.2
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 0.10.1, 0.10.2, 0.11.1, 0.11.2, 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt j...@apache.org wrote: Should we hold 1.0.2 for this? If releases are a whole bunch of work, then yes. However, since this doesn't seem to be a (recent) regression, it would IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this thing is fixed. Cheers, Dirkjan
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On Sun, Nov 28, 2010 at 1:52 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt j...@apache.org wrote: Should we hold 1.0.2 for this? If releases are a whole bunch of work, then yes. However, since this doesn't seem to be a (recent) regression, it would IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this thing is fixed. There was a separate issue in the CHANGES and NEWS that were enough to veto the 1.0.2 artefacts. I'd vote to just wait for this to get sussed out before moving forward with 1.0.2 again. Paul Cheers, Dirkjan
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
I don't think we should make a release when we have a known and serious bug. On Sun, Nov 28, 2010 at 7:55 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Sun, Nov 28, 2010 at 1:52 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt j...@apache.org wrote: Should we hold 1.0.2 for this? If releases are a whole bunch of work, then yes. However, since this doesn't seem to be a (recent) regression, it would IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this thing is fixed. There was a separate issue in the CHANGES and NEWS that were enough to veto the 1.0.2 artefacts. I'd vote to just wait for this to get sussed out before moving forward with 1.0.2 again. Paul Cheers, Dirkjan
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
I hope that identifying and fixing the issue doesn't take weeks but days. I don't think it's worth the trouble releasing two versions so quickly after another. Since 1.0.2 is only a patch I'd suggest to wait. On 28.11.2010, at 20:52, Dirkjan Ochtman wrote: On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt j...@apache.org wrote: Should we hold 1.0.2 for this? If releases are a whole bunch of work, then yes. However, since this doesn't seem to be a (recent) regression, it would IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this thing is fixed. Cheers, Dirkjan
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On Sun, Nov 28, 2010 at 8:58 PM, Robert Newson robert.new...@gmail.com wrote: I don't think we should make a release when we have a known and serious bug. +1
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
On 28 Nov 2010, at 20:58, Robert Newson wrote: I don't think we should make a release when we have a known and serious bug. I agree. Cheers Jan -- On Sun, Nov 28, 2010 at 7:55 PM, Paul Davis paul.joseph.da...@gmail.com wrote: On Sun, Nov 28, 2010 at 1:52 PM, Dirkjan Ochtman dirk...@ochtman.nl wrote: On Sun, Nov 28, 2010 at 13:55, Jan Lehnardt j...@apache.org wrote: Should we hold 1.0.2 for this? If releases are a whole bunch of work, then yes. However, since this doesn't seem to be a (recent) regression, it would IMHO be even greater if we had this 1.0.2 and a quick 1.0.3 once this thing is fixed. There was a separate issue in the CHANGES and NEWS that were enough to veto the 1.0.2 artefacts. I'd vote to just wait for this to get sussed out before moving forward with 1.0.2 again. Paul Cheers, Dirkjan
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Cohnen updated COUCHDB-968:
-
Description:
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c all
system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10 IDs
which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
since the two new servers were meant to replace the old ones (to update node.js
application code among other things).
was:
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c all
system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10 IDs
which sum up to a total of 922 duplicates. Some of them have only 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
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Priority: Blocker (was: Major)
Bob, in tisba's case the duplicates had the same revision. Is that also true
in your case? And you only see these duplicates after compaction?
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
Re: [jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
yea, they are identical and both compaction and exceeding the revision max is
required to reproduce.
On Nov 27, 2010, at 5:45 PM, Adam Kocoloski (JIRA) wrote:
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Kocoloski updated COUCHDB-968:
---
Priority: Blocker (was: Major)
Bob, in tisba's case the duplicates had the same revision. Is that also true
in your case? And you only see these duplicates after compaction?
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
Priority: Blocker
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs
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
found 10 IDs which sum up to a total of 922 duplicates. Some of them have
only 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=false on all nodes
* used couchdb versions 1.0.0 and 1.0.x (*)
Unfortunately the database's contents are confidential and I'm not allowed
to publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
[*]
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 servers
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.
[jira] Updated: (COUCHDB-968) Duplicated IDs in _all_docs
[
https://issues.apache.org/jira/browse/COUCHDB-968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebastian Cohnen updated COUCHDB-968:
-
Affects Version/s: 1.0
Duplicated IDs in _all_docs
---
Key: COUCHDB-968
URL: https://issues.apache.org/jira/browse/COUCHDB-968
Project: CouchDB
Issue Type: Bug
Components: Database Core
Affects Versions: 1.0, 1.0.1, 1.0.2
Environment: Ubuntu 10.04.
Reporter: Sebastian Cohnen
We have a database, which is causing serious trouble with compaction and
replication (huge memory and cpu usage, often causing couchdb to crash b/c
all system memory is exhausted). Yesterday we discovered that db/_all_docs 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 found 10
IDs which sum up to a total of 922 duplicates. Some of them have only 1
duplicate, others have hundreds.
Some facts about the database in question:
* ~13k documents, with 3-5k revs each
* compaction is run on a daily bases
* several thousands updates per hour
* multi-master setup with pull replication from each other
Unfortunately the database's contents are confidential and I'm not allowed to
publish it.
[1]: Part of http://localhost:5984/DBNAME/_all_docs
...
{id:9997,key:9997,value:{rev:6096-603c68c1fa90ac3f56cf53771337ac9f}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
{id:,key:,value:{rev:6097-3c873ccf6875ff3c4e2c6fa264c6a180}},
...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
