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

Replica Node Never Becomes Secondary after Recovering

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

      Configuration - MongoDB with three nodes : Primary , Secondary,1 Secondary2

      When we shutdown secondary1 node and do not bring it up for long time (say more the 10 mins) then in the output of rs.status() we will see that secondary1 is in RECOVERING state and it doesn't resume into state SECONDARY until we do not perform the manual resync steps (by empyting the data directory and restart process)

      Referred https://jira.mongodb.org/browse/SERVER-26360 but can't get the exact RCA or fix.

            Assignee:
            kelsey.schubert@mongodb.com Kelsey Schubert
            Reporter:
            pratiksha.gupta38@gmail.com Pratiksha Aggarwal
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: