Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-5975

Add option to replSetReconfig to tell it that a new node being added already has a copy of the data

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None

    Description

      A common use case is taking a snapshot of production and using that to seed a staging environment. The problem is that the snapshot contains the replica set configuration for the production machines, not the hosts of the staging environment. Currently, if you bring up the staging environment from the snapshots and try to run replSetReconfig on one to give it the new configuration for the staging environment, the command fails complaining that the other nodes being added to the set already have data on them. If we had this option, we could tell the command to trust that the other nodes have a valid copy of the data, and skip the initial sync phase (possibly after some verification that the oplogs are the same).

      Attachments

        Activity

          People

            Unassigned Unassigned
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: