[SERVER-11383] Prevent copydb to/from local database Created: 25/Oct/13  Updated: 06/Dec/22  Resolved: 20/Sep/18

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Backlog - Replication Team
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-8511 Live oplog can be dropped Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:

 Description   

Currently if you use copydb to copy the local database from one replica set member to another replica set member, the oplog entries get copied over without applying the associated writes to the user data. This could cause your oplog and your data to get out of sync, potentially causing serious problems.



 Comments   
Comment by Gregory McKeon (Inactive) [ 20/Sep/18 ]

This has gone away with the removal of copydb.

Comment by Spencer Brody (Inactive) [ 05/Mar/14 ]

Yep, and agreed.

Comment by Eric Milkie [ 05/Mar/14 ]

Do you mean using copydb to copy the local db from a secondary to the primary? That would be really bad.
I think this should be generalized to say that the special collections in local that are used by replication should be specially protected against non-internal writes.

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