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

Replica set recovery doesn't happen immediately at boot with 3.2 as it did with <3.2

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.2.4
    • Component/s: Replication
    • None
    • ALL
    • Hide

      Set up replica set with 2 nodes and an arbiter. Kill the primary. Start it back up with a empty data directory.

      Show
      Set up replica set with 2 nodes and an arbiter. Kill the primary. Start it back up with a empty data directory.

      Had to recover an instance today that was previously the primary in a replica set (2+arb). Followed the same procedure that I've used in past with lightly loaded instances - started with an empty data directory.

      In the past, this would immediately start recovering from the standby instance. With this current 3.2.4 deployment, it sat there for a bit over 3 minutes before it started recovery/rebuild process.

      Is that expected with 3.2 or some new tuning parameter?

        1. log-c-mosaic-db2.txt.gz
          10 kB
        2. log-c-mosaic-db1.txt.gz
          687 kB
        3. log-c-mosaic-arb.txt.gz
          6 kB

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            nneul@sevogle.com Nathan Neulinger
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: