Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-6658

Steps for converting master/slave deployment to replica set should suggest dropping local database

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • Server_Docs_20231030
    • mongodb-2.6, mongodb-3.0
    • manual, Server
    • None

    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 ($).

      Attachments

        Activity

          People

            kay.kim@mongodb.com Kay Kim (Inactive)
            stephen.steneker@mongodb.com Stennie Steneker (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              1 year, 14 weeks, 1 day ago