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

after replica set members restarted, they go into recovery spin

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Works as Designed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Environment:
      64 bit Window
    • Operating System:
      ALL

      Description

      I had a 3 member replica set running on my laptop. Small database, only used for training class.

      Had to reboot the laptop.

      After rebooting, restarted the replica set members. What had been the primary recovered, became a secondary, and waited for the other members, according to rs.status().

      What had been secondaries went into some kind of recovery spin, creating many 2G local.N files, until I finally killed them.

      Logs for the three servers from the point of restart are attached.

        Attachments

        1. mongodb.log
          111 kB
        2. mongodb.log
          2 kB
        3. mongodb.log
          2 kB

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: