-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
None
-
Affects Version/s: 2.6.0-rc1
-
Component/s: Index Maintenance, Storage
-
ALL
-
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
- is related to
-
SERVER-8412 repairDatabase: no Cloner, and use multi index builder
- Closed
- related to
-
SERVER-21751 Change _id format in local.startup_log collection to avoid duplicate key errors in systems missing RTC
- Backlog