[SERVER-26599] Master-slave initial sync should use the exact _id index spec from master Created: 12/Oct/16  Updated: 19/Nov/16  Resolved: 18/Oct/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.4.0-rc1

Type: Bug Priority: Blocker - P1
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-26513 listCollections output should include... Closed
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Steps To Reproduce:

var rt = new ReplTest();
 
var m = rt.start(true);
var s = rt.start(false);
 
sleep(5000);
 
var masterCollInfo = m.getDB("admin").getCollectionInfos({name: "system.version"})[0];
var slaveCollInfo = s.getDB("admin").getCollectionInfos({name: "system.version"})[0];
 
// fails
assert.eq(masterCollInfo, slaveCollInfo);
 
rt.stop();

Sprint: Query 2016-10-31
Participants:
Linked BF Score: 0

 Description   

The slave creates the default _id index spec for the collection here. Instead, it should copy the exact _id index spec from master.



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

Author:

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

Message: SERVER-26599 Master-slave initial sync should use the exact _id index spec from master
Branch: master
https://github.com/mongodb/mongo/commit/5053052fdafc16e7027cb246ce58c300bb6f45b5

Comment by Eric Milkie [ 12/Oct/16 ]

I think the clone and copyDb commands use that same code path, and thus are similarly affected.

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