Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-6376

as long as oplog window on any replica set members can span back to the snapshot’s timestamp, seeding a secondary will work

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Minor - P4 Minor - P4
    • 01112017-cleanup
    • None
    • Cloud Manager
    • None

    Description

      This is the current documentation about seeding a secondary

      *https://docs.opsmanager.mongodb.com/current/tutorial/use-restore-to-seed-secondary/#considerations
      *https://docs.cloud.mongodb.com/tutorial/use-restore-to-seed-secondary/#considerations

      In these documentation, there is a paragraph as follows

      "Seeding a new secondary from a backup restore requires an oplog window on the current primary that spans back to the snapshot’s timestamp."

      It's not true. Seeding a new secondary does not require oplog window on current primary. As long as the oplog window of any replica set member is sufficient, seeding a new secondary will work.

      Therefore, we advise to change it to

      "Seeding a new secondary from a backup restore requires an oplog window on at least one replica set member that spans back to the snapshot’s timestamp."

      Attachments

        Activity

          People

            bgrabar Bob Grabar
            jun.wan Jun Wan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:
              8 years, 18 weeks ago