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

add support to OplogFetcher for restarting oplog query

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.3.10
    • Fix Version/s: 3.3.15
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Steps To Reproduce:
      Hide

      The OplogFetcher should restart up to N (10) times before failing.

      Show
      The OplogFetcher should restart up to N (10) times before failing.
    • Sprint:
      Repl 2016-09-19, Repl 2016-10-10
    • Linked BF Score:
      0

      Description

      2016-08-18T21:32:21.909+0000 E REPL     [replication-1] Error fetching oplog during initial sync: ExceededTimeLimit: operation exceeded time limit
      2016-08-18T21:32:21.922+0000 I REPL     [initial sync] Initial sync finished applying oplog entries.
      2016-08-18T21:32:22.584+0000 I REPL     [InitialSyncInserters-config.migrations0] done running the synchronous task.
      2016-08-18T21:32:23.035+0000 I REPL     [repl writer worker 5] data clone finished, status: CallbackCanceled: Initial Sync Cancelled.
      2016-08-18T21:32:23.123+0000 E REPL     [initial sync] Initial sync attempt failed -- attempts left: 9 cause: ExceededTimeLimit: operation exceeded time limit
      

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: