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

After node goes into RECOVERING due to being too stale to sync from its source, it will never recover even if there is a valid sync source it could use

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.4.5, 3.5.6
    • Affects Version/s: None
    • Component/s: Replication
    • Fully Compatible
    • ALL
    • v3.4
    • Repl 2017-03-06, Repl 2017-03-27, Repl 2017-04-17
    • 35

      If a node is syncing from another node and has no common point in its oplog, it will go into RECOVERING state due to being 'too stale'. It will never leave recovering, even if there is another node it could sync from which does have a common point.

      I have attached a cleaned up and extended version of the toostale.js test that demonstrates this issue.

        1. toostale.js
          3 kB
          Spencer Brody

            Assignee:
            william.schultz@mongodb.com Will Schultz
            Reporter:
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: