[SERVER-5963] exception cloning object in replset7.js Created: 30/May/12  Updated: 11/Jul/16  Resolved: 03/Jun/12

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 2.1.2

Type: Bug Priority: Major - P3
Reporter: Ian Whalen (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: buildbot
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-5040 Cloner can fail to create unique inde... Closed
Operating System: ALL
Participants:

 Description   

	
 m31001| Wed May 30 09:32:40 [rsSync] build index d.c { _id: 1 }
 m31001| Wed May 30 09:32:41 [rsSync] 	 fastBuildIndex dupsToDrop:0
 m31001| Wed May 30 09:32:41 [rsSync] build index d.c { x: 1.0 }
 m31001| Wed May 30 09:32:41 [rsSync] build index done.  scanned 50477 total records. 0.976 secs
 m31001| Wed May 30 09:32:42 [FileAllocator] allocating new datafile /data/db/replset7tests-1/d.1, filling with zeroes...
 m31001| Wed May 30 09:32:43 [FileAllocator] done allocating datafile /data/db/replset7tests-1/d.1, size: 32MB,  took 0.098 secs
 m31001| Wed May 30 09:32:43 [rsSync] ERROR: error: exception cloning object in d.system.indexes E11000 duplicate key error index: d.c.$x_1  dup key: { : 44293.0 } obj:{ key: { x: 1.0 }, unique: true, ns: "d.c", name: "x_1" }
 m31001| Wed May 30 09:32:43 [rsSync] datafileheader::init initializing /data/db/replset7tests-1/d.1 n:1
 m31001| replSet initial sync exception: 11000 E11000 duplicate key error index: d.c.$x_1  dup key: { : 44293.0 } 0 attempts remaining

http://buildlogs.mongodb.org/build/4fc61fe4d2a60f4fb300003e/test/4fc61fe5d2a60f4fc2000035/



 Comments   
Comment by auto [ 03/Jun/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5963 - fix dbtests for capped indexes
Branch: master
https://github.com/mongodb/mongo/commit/87dbe44764b11117723c2c0ca96c212fdcc97c31

Comment by auto [ 03/Jun/12 ]

Author:

{u'login': u'erh', u'name': u'Eliot Horowitz', u'email': u'eliot@10gen.com'}

Message: SERVER-5963 change order of initial sync so that we do data, then sync,
then indexes, then sync again to make sure indexes work well
Branch: master
https://github.com/mongodb/mongo/commit/787fcbb20b08cff122e43bacdd74b1d87d8930fd

Comment by Eliot Horowitz (Inactive) [ 30/May/12 ]

This is fixed in a mildly ugly way.

Generated at Thu Feb 08 03:10:23 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.