[SERVER-26764] Do not defer creation of _id index for replicated collections Created: 25/Oct/16  Updated: 31/Oct/16  Resolved: 28/Oct/16

Status: Closed
Project: Core Server
Component/s: Querying, Replication, Sharding
Affects Version/s: None
Fix Version/s: 3.4.0-rc2

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-26515 Create collection with v=2 index shou... Closed
Related
related to SERVER-26834 replset7.js should cause documents to... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Query 2016-10-31, Query 2016-11-21
Participants:
Linked BF Score: 0

 Description   

When a primary defers creation of the _id index, the secondary still creates the _id index when applying the oplog entry for the collection creation. This results in inconsistent indexes between primary and secondary. We should remove occurrences of deferred _id index creation:
chunk migration
cloner (all occurrences in that file)
renameCollection
repairDatabase (mmapv1)

We need not change initial sync or the oplog buffer collection, since those collection creations are not replicated.



 Comments   
Comment by Githook User [ 28/Oct/16 ]

Author:

{u'username': u'tessavitabile', u'name': u'Tess Avitabile', u'email': u'tess.avitabile@mongodb.com'}

Message: SERVER-26764 Do not defer creation of _id index for replicated collections
Branch: master
https://github.com/mongodb/mongo/commit/8ac6f69b0879df0e69b8d9929badb472772a3bca

Generated at Thu Feb 08 04:13:08 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.