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

Starting MongoDB using snapshot data on PIOPS volumes on Amazon EC2 environment

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Incomplete
    • Affects Version/s: 2.2.2
    • Fix Version/s: None
    • Component/s: Internal Code
    • Labels:
      None
    • Environment:
      linux
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      1.Setup a mongodb cluster on Amazon EC2 linux instances.
      2. Once the cluster is up start the load on the db.
      3. After the loading is completed stop all the mongo processes and take a snapshot of shard servers and config servers.
      4. After snapshot is completed create new volumes and attach to the corresponding instances and start the cluster.

      Show
      1.Setup a mongodb cluster on Amazon EC2 linux instances. 2. Once the cluster is up start the load on the db. 3. After the loading is completed stop all the mongo processes and take a snapshot of shard servers and config servers. 4. After snapshot is completed create new volumes and attach to the corresponding instances and start the cluster.

      Description

      Hi,

      We have a mongodb sharded cluster which was having a sharded database named "mydb" and loaded 333GB of data.
      Once the total data is loaded, we have stopped all the mongod processes for shards, mongod processes for config servers and mongos process on all routers.
      Then we have taken snapshots of all the volumes of the cluster. Then we have created volumes from the snapshots.
      We have mounted volumes on the corresponding shards, config servers and started the processes.

      Observations:

      All the shards came up and the data is in tact. able to see the records present in the shards.
      Then started config servers and routers. Router is able to add only shard1 and when tried to add other shards getting the following error message.

      mongos> db.runCommand(

      { addshard : "shard2/10.10.10.10:27018" }

      );
      {
      "ok" : 0,
      "errmsg" : "can't add shard shard2/10.10.10.10:27018 because a local database 'mydb' exists in another shard1:shard1/10.10.10.1:27018,10.10.10.2:27018,10.10.10.3:27018"
      }

      Please let me know if we are missing anything here?

        Attachments

          Activity

            People

            Assignee:
            barrie Barrie Segal
            Reporter:
            krisant007 Santosh Kumar L
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: