[DOCS-6658] Steps for converting master/slave deployment to replica set should suggest dropping local database Created: 27/Nov/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | mongodb-2.6, mongodb-3.0 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Stennie Steneker (Inactive) | Assignee: | Kay Kim (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||||||
| Epic Link: | DOCSP-1769 | ||||||||
| Description |
|
The procedure for converting a master/slave deployment to a replica set is missing a step to remove the local database before initiating the replica set: https://docs.mongodb.org/manual/core/master-slave/#convert-a-master-slave-deployment-to-a-replica-set. This should happen after the backup taken in step 3 but before the current step 4 (which restarts mongod with --replSet). Since newer versions of the MongoDB server have stronger enforcement for collection name validation, it isn't possible to later drop or rename the legacy master/slave oplog collection (local.oplog.$main) because it includes a reserved character ($). |
| Comments |
| Comment by Education Bot [ 01/Nov/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! |