-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Major - P3
-
None
-
Affects Version/s: 1.8.1, 2.0.2, 2.0.4
-
Component/s: Index Maintenance
-
None
-
Environment:Linux 2.6.32-5-amd64 #1 SMP x86_64 GNU/Linux
debian 6.0.1
-
Linux
An index , other than "id" on a capped collection can grow with no limitation, and it's space never reused.
I have a capped collection with 7 indexes which was capped to 16G. in several days it's indexes reached 24G in size.
Furthermore, when I ran a validate command on 16G collection (with 24G indexes) - mongod server crashed.
Here is an example on a smaller collection with the same indexes, which I ran with a difference of several minutes:
db.coll1.stats();
{
"ns" : "db1.coll1",
"count" : 2746628,
"size" : 1029799416,
"avgObjSize" : 374.93225001711187,
"storageSize" : 1073745920,
"numExtents" : 1,
"nindexes" : 8,
"lastExtentSize" : 1073745920,
"paddingFactor" : 1,
"flags" : 1,
"totalIndexSize" : 1726918368,
"indexSizes" : {
"_id_" : 89142928,
"date_-1" : 199666096,
"date_updated_-1" : 192160528,
"level_1" : 110376000,
"date_updated_-1_level_1" : 247332176,
"date_-1_facility_1" : 221119920,
"date_-1_host_1_facility_1" : 323229984,
"date_updated_-1_host_1_level_1" : 343890736
},
"capped" : 1,
"max" : 2147483647,
"ok" : 1
}
several minutes later:
db.coll1.stats();
{
"ns" : "db1.coll1",
"count" : 2746972,
"size" : 1029794112,
"avgObjSize" : 374.88336684902504,
"storageSize" : 1073745920,
"numExtents" : 1,
"nindexes" : 8,
"lastExtentSize" : 1073745920,
"paddingFactor" : 1,
"flags" : 1,
"totalIndexSize" : 1728529040,
"indexSizes" : {
"_id_" : 89142928,
"date_-1" : 199935904,
"date_updated_-1" : 192422160,
"level_1" : 110343296,
"date_updated_-1_level_1" : 247479344,
"date_-1_facility_1" : 221455136,
"date_-1_host_1_facility_1" : 323614256,
"date_updated_-1_host_1_level_1" : 344136016
},
"capped" : 1,
"max" : 2147483647,
"ok" : 1
}
also I was trying to bring the extent information for this collection - but the server crashes again (log of that crash attached)
- related to
-
-
- Closed
-