[SERVER-13146] An _id index is built on the local.startup_log collection by default Created: 11/Mar/14  Updated: 03/Dec/15  Resolved: 12/Mar/14

Status: Closed
Project: Core Server
Component/s: Index Maintenance, Storage
Affects Version/s: 2.6.0-rc1
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kamran K. Assignee: Unassigned
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-21751 Change _id format in local.startup_lo... Backlog
is related to SERVER-8412 repairDatabase: no Cloner, and use mu... Closed
Operating System: ALL
Steps To Reproduce:

db.getSiblingDB('local').startup_log.getIndexes();

Participants:

 Description   

In 2.4.9, an _id index is not automatically created on the local.startup_log collection. In master, an _id index is created by default. This is a regression caused by the changes from SERVER-8412.

2.4.9:

> db.getSiblingDB('local').startup_log.getIndexes()
[ ]

master:

> db.getSiblingDB('local').startup_log.getIndexes()
[
	{
		"v" : 1,
		"key" : {
			"_id" : 1
		},
		"name" : "_id_",
		"ns" : "local.startup_log"
	}
]


Version: 575c9cbe27ba6b9ba56b810e42508d120ae44a94


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