-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
None
-
Affects Version/s: 2.2.0
-
Component/s: Replication
-
Environment:Ubuntu 12.04 64 bits x86
-
Linux
Hello,
I'm facing a big issue in my production environment.
I'v moved my standalong existing database into a replica set, and my secondary instance always failed in its initial synchronization phase.
The failing happend on a collection named record, where indexes are defined below :
nws_rs_1:PRIMARY> db.record.getIndexSpecs()
[
{
"v" : 1,
"key" :
,
"ns" : "nadb.record",
"name" : "id"
},
{
"v" : 1,
"key" :
,
"unique" : true,
"ns" : "nadb.record",
"name" : "id.L_1_id.K_1",
"dropDups" : true
}
]
nws_rs_1:PRIMARY> db.record.stats()
{
"ns" : "nadb.record",
"count" : 1605239,
"size" : 4816750020,
"avgObjSize" : 3000.643530340342,
"storageSize" : 8696713216,
"numExtents" : 33,
"nindexes" : 2,
"lastExtentSize" : 1940869120,
"paddingFactor" : 1.0040000005010514,
"systemFlags" : 0,
"userFlags" : 0,
"totalIndexSize" : 145295696,
"indexSizes" :
,
"ok" : 1
}
And the secondary always fails with message:
Thu Oct 25 11:46:21 [repl writer worker 4] Fatal Assertion 15915
(full log trace in uploaded message)
This is a big issue since I can't set any replication mechanism !
Thank you for you help.
Thomas.