An _id index is built on the local.startup_log collection by default

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Minor - P4
    • None
    • Affects Version/s: 2.6.0-rc1
    • Component/s: Index Maintenance, Storage
    • ALL
    • Hide 
      db.getSiblingDB('local').startup_log.getIndexes();
      Show
      db.getSiblingDB('local').startup_log.getIndexes();
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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

            Assignee:
            Unassigned
            Reporter:
            Kamran K. (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: