Add guardrail to detect new oplog entries being written by secondary

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • 8.3 Required
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In SERVER-108462 we saw a case where a node could write down a new oplog entry as a secondary.

      While SERVER-108462 will fix that particular instance, we should add guardrails to catch this generally. For example, a node should not be able to reserve an optime if Intent::LocalWrite has been registered.

            Assignee:
            Unassigned
            Reporter:
            Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: