[DOCS-14336] Rename ReplicaSet Created: 06/Apr/21 Updated: 30/Oct/23 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Александр Малков | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 2 days ago |
| Epic Link: | DOCSP-11701 |
| Description |
DescriptionHi! I have a replica set of three nodes, and I want rename it. The documentation https://docs.mongodb.com/manual/tutorial/rename-unsharded-replica-set/ says that in order to rename a replica set I have to:
The backup is needed as insurance against incorrect actions when renaming a replica set.
During times 1 and 2, the set is available for writing and reading. At time 3, it is read-only. i tested this on 4.2+ versions with C# driver. This way, I minimize the time the replica set is unavailable until the restart time of the two nodes. Why is my varinat dangerous? What problems can arise if you do this? Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Education Bot [ 31/Oct/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |
| Comment by Jeffrey Allen [ 17/May/21 ] |
|
Hello malkov@skbkontur.ru, thank you for filing this ticket. I will run this by our engineering team and try to get you an answer soon. |
| Comment by Александр Малков [ 17/May/21 ] |
|
Hey! The question is still relevant. |