[DOCS-9578] Docs for SERVER-17710: Do not automatically wipe existing data before initial sync Created: 05/Dec/16  Updated: 27/Oct/23  Resolved: 21/Jan/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Emily Hall Assignee: Unassigned
Resolution: Works as Designed Votes: 0
Labels: initialization, replicaset
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 6 years, 3 weeks, 4 days ago
Epic Link: PM-248

 Description   

Engineering Ticket Description:

When running rs.initiate(), if any nodes other than the initiator node have data (but not an oplog), an error results:

"errmsg" : "couldn't initiate : member <node> has data already, cannot initiate set.  All members except initiator must be empty."

If you later use rs.add() to a node that has data (but not an oplog), then it will cause that node to initial sync and throw no errors.

If you can rs.add() a node with data in it, it follows that you should be able to have a configuration object for rs.initiate() that contains a node with data in it (and both should cause an initial sync of that node).



 Comments   
Comment by Kay Kim (Inactive) [ 21/Jan/18 ]

Overly aggressive ticket creation by the ticket maker script.

Generated at Thu Feb 08 07:58:41 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.