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

Replica Set SECONDARY Fails to Come Online Following Full Re-Sync

    • Type: Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 2.4.2, 2.4.3
    • Component/s: Replication
    • Environment:
      All three servers: Windows 2008 R2 64-bit, Dual Quad-Core Intel Xeon X3450, 4 GB , 183 GB Hard Drive
    • Windows

      I have a simple replica set with a primary a secondary and an arbiter. I experienced a hardware failure a few days ago which required provisioning a brand new machine to replace one of the primary/secondary servers.

      I setup the server with the same IPs as the previous server and started up Mongo with an empty data directory to allow it to perform a full re-sync.

      Each time I tried the full re-sync it would successfully sync all the data but I believe it is at the point at which it attempts to apply the oplog before actually coming up as a secondary that it failed each time until I downgraded the secondary to 2.2.4. At that point (without having to fully re-sync again) everything came up as expected.

      I have attached PRIMARY and SECONDARY logs for the appropriate timeframes to show from start of sync through the failure. I also included the log of the SECONDARY after I downgraded to 2.2.4 and what it did following.

      Please let me know if I need to provide other information.

            thomas.rueckstiess@mongodb.com Thomas Rueckstiess
            adam.kirkton Adam Kirkton
            0 Vote for this issue
            5 Start watching this issue