[SERVER-5883] duplicate key error in replset7.js Created: 21/May/12  Updated: 11/Jul/16  Resolved: 21/May/12

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

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

Linux 64-bit debug dur off


Operating System: ALL
Participants:

 Description   

 m31001| Sun May 20 13:01:26 [FileAllocator] allocating new datafile /data/db/replset7tests-1/d.1, filling with zeroes...
 m31001| Sun May 20 13:01:26 [FileAllocator] done allocating datafile /data/db/replset7tests-1/d.1, size: 32MB,  took 0.018 secs
 m31001| Sun May 20 13:01:26 [rsSync] datafileheader::init initializing /data/db/replset7tests-1/d.1 n:1
 m31001| Sun May 20 13:01:27 [rsSync] build index d.c { _id: 1 }
 m31001| Sun May 20 13:01:28 [rsSync] 	 fastBuildIndex dupsToDrop:0
 m31001| Sun May 20 13:01:28 [rsSync] build index done.  scanned 100348 total records. 0.934 secs
 m31001| Sun May 20 13:01:28 [rsSync] build index d.c { x: 1.0 }
 m31001| Sun May 20 13:01:28 [rsSync] ERROR: error: exception cloning object in d.system.indexes E11000 duplicate key error index: d.c.$x_1  dup key: { : 99652.0 } obj:{ key: { x: 1.0 }, unique: true, ns: "d.c", name: "x_1" }
 m31001| replSet initial sync exception: 11000 E11000 duplicate key error index: d.c.$x_1  dup key: { : 99652.0 } 0 attempts remaining
 m31001| Sun May 20 13:01:50 [conn6] end connection 174.121.165.194:51072 (2 connections now open)
 m31001| Sun May 20 13:01:50 [initandlisten] connection accepted from 174.121.165.194:51076 #7 (4 connections now open)
 m31001| Sun May 20 13:01:52 [clientcursormon] mem (MB) res:92 virt:403 mapped:160
 m31001| Sun May 20 13:01:58 [rsSync]   Fatal Assertion 16233
 m31001| 0xbe181f 0xd1bfcf 0xd4206a 0x8b3a5f 0xac0b25 0xc8a0ff 0xc8a1f6 0xc8a4c4 0x8aa5f7 0xdda1bc 0x7fbfabcc6a04 0x7fbfab07cd4d 
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo15printStackTraceERSo+0x27) [0xbe181f]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo12sayDbContextEPKc+0x5e) [0xd1bfcf]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo13fassertFailedEi+0x65) [0xd4206a]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo7fassertEib+0x25) [0x8b3a5f]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo11ReplSetImpl17syncDoInitialSyncEv+0x1c5) [0xac0b25]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo11ReplSetImpl11_syncThreadEv+0xc7) [0xc8a0ff]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo11ReplSetImpl10syncThreadEv+0x9c) [0xc8a1f6]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5mongo15startSyncThreadEv+0xb4) [0xc8a4c4]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod(_ZN5boost6detail11thread_dataIPFvvEE3runEv+0x19) [0x8aa5f7]
 m31001|  /home/yellow/buildslave/Linux_64bit_debug_dur_off/mongo/mongod [0xdda1bc]
 m31001|  /lib/libpthread.so.0 [0x7fbfabcc6a04]
 m31001|  /lib/libc.so.6(clone+0x6d) [0x7fbfab07cd4d]
 m31001| Sun May 20 13:01:58 [rsSync] 
 m31001| 
 m31001| ***aborting after fassert() failure

Probably https://github.com/mongodb/mongo/commit/161960373175779914c093be70fa06dde3b60909

http://buildbot.mongodb.org/builders/Linux%2064-bit%20debug%20dur%20off/builds/1242/steps/test_7/logs/stdio



 Comments   
Comment by Eric Milkie [ 21/May/12 ]

git commit 03cd7b93e666d80a3640171ba1af8407b0591591

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