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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.5, 3.5.6
    • Component/s: Replication
    • Labels:
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-03-06, Repl 2017-03-27, Repl 2017-04-17
    • Linked BF Score:
      35

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                1 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: