[SERVER-5779] mongorestore from a secondary breaks replication Created: 07/May/12  Updated: 30/May/12  Resolved: 30/May/12

Status: Closed
Project: Core Server
Component/s: Replication, Tools
Affects Version/s: 2.0.4
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Chris Westin Assignee: Gregor Macadam
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Windows


Attachments: Text File SERVER-5779-transcript.txt    
Operating System: ALL
Participants:

 Description   

This happened in an admin training class.

After the backup section, student used mongodump to create a backup of a secondary (from a replica set we had previously set up on everyone's laptops; for data, imagine importing the training data set and making a few changes to it).

Then, the student used mongorestore --drop to restore the dump onto their primary. At this point, their secondaries went into RECOVERING state, and never came back. Their last optimes (via rs.status()) were shown to be about the time the restore was performed.



 Comments   
Comment by Gregor Macadam [ 30/May/12 ]

Unable to repro Windows 7 Pro N, mongo 2.0.4
Transcript attached.

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