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

Keep fetching oplog during index creation of initial resync

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Replication
    • None

    Description

      When doing an initial resync for a secondary where large indexes are created it easily ends up to a "too stale" state as the primary's oplog is too small. When the index creation takes several days the oplog size would have to be enormous to handle it or you'd have to take another secondary down to copy the files over.

      Why not just keep fetching the oplog during the index creation instead of trying to fetch them all after the indexes are created?

      Attachments

        Issue Links

          Activity

            People

              backlog-server-repl Backlog - Replication Team
              devastor Tuomas Silen
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: