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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Replication
    • ALL
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Spencer Brody (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: