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

Unexpected Initial Sync on Replicaset

    • Type: Icon: Question Question
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:

      Trying to add a MongoDB 3.0 instance to an existing MongoDB 2.6 replica set. Following the instructions on how to do this I tried the following steps.

      From the Primary, called 1e-26, I added the new instance "1c:27107" to the replica set.
      Took an EBS snapshot of data volume of 1e-26
      Stopped the mongod service on new instance, 1c.
      Created an EBS volume of from the 1e-26 snapshot.
      Attached the volume to 1c as the new data volume
      Restarted the mongod service

      I expected 1c to use the data from the snapshot to speed up the sync with 1e-26, but instead it removes all the data and starts and initial sync. We cannot upgrade to MongoDB 3+ until we can solve the problem of how to restore a MongoDB instance from an EBS Snapshot.

      With MongoDB 2.6 and prior. It was a simple matter to start a mongd service with the latest EBS snapshot and add the new instance from the primary. This approach no longer works.

      Attached are the log files from 1e-26, 1c and the configs

        1. 1c.log
          510 kB
        2. 1e-26.log
          1.18 MB
        3. mongod3-0.conf
          0.4 kB
        4. mongodb2-6.conf
          0.3 kB
        5. original_mail_comment.txt
          64 kB

            kelsey.schubert@mongodb.com Kelsey Schubert
            justronin Ralph Decatrel
            0 Vote for this issue
            5 Start watching this issue