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

Secondary can refuse to sync from primary that is ahead of it, preventing it from ever rolling back

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • ALL
    • 0

    Description

      If a secondary has no sync source, but there is a valid primary it can/should be syncing from, but that primary has an older optime than it does, the secondary will never select a sync source, and thus will never go into rollback as it should.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            spencer@mongodb.com Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: