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

shouldRetry() logic in multiInitialSyncApply_noAbort() is over-aggressive

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.7, 3.5.10
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.4
    • Sprint:
      Repl 2017-05-08, Repl 2017-05-29, Repl 2017-06-19, Repl 2017-07-31

      Description

      Currently multiInitialSyncApply_noAbort() calls shouldRetry() on all !OK statuses returned from applying any non-command op. If shouldRetry() returns false, the error is ignored. It should probably only do this for error cases that are expecting the shouldRetry() treatment (such as an update not finding a document) rather than for absolutely all errors.

        Attachments

          Activity

            People

            Assignee:
            judah.schvimer Judah Schvimer
            Reporter:
            redbeard0531 Mathias Stearn
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: