[SERVER-7829] Indexes are not maintained in oplog/profile capped collections Created: 03/Dec/12  Updated: 10/Dec/14  Resolved: 21/Apr/14

Status: Closed
Project: Core Server
Component/s: Index Maintenance
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Unassigned
Resolution: Duplicate Votes: 1
Labels: capped, collection, oplog, profiling
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-7107 Queries/getmores generate write lock ... Closed
related to SERVER-12201 do not allow index entries on local.o... Closed
related to SERVER-11611 remove DataFileMgr::insert* Closed
Operating System: ALL
Participants:

 Description   

No indexes are updated on inserts (fast_oplog_insert does not update indexes).

> db.system.profile.ensureIndex({ns:1})
> db.system.profile.find({}).hint({ns:1}).explain()
{
	"cursor" : "BtreeCursor ns_1",
	"isMultiKey" : false,
	"n" : 8,
	... }
> db.system.profile.find({}).hint({ns:1}).explain()
{
	"cursor" : "BtreeCursor ns_1",
	"isMultiKey" : false,
	"n" : 8,
	... }
...
> db.system.profile.count()
12
...
> db.system.profile.count()
14
> db.system.profile.find({}).hint({ns:1}).explain()
{
	"cursor" : "BtreeCursor ns_1",
	"isMultiKey" : false,
	"n" : 8,
	... }



 Comments   
Comment by J Rassi [ 21/Apr/14 ]

Resolving as dup of SERVER-12201 (disallows indexes on the oplog), SERVER-11611 (restores correct behavior to system.profile indexes).

Comment by Vladimir Malyk [ 20/Aug/13 ]

looks like it is related to https://jira.mongodb.org/browse/PHP-799 issue

Comment by Scott Hernandez (Inactive) [ 03/Dec/12 ]

It should either disallow creating indexes or keep them up to date (and not use fast_oplog_insert for example).

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