Remove oldestOplogEntryTS invariants when we allow txns larger than 16MB

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: Needs Triage
    • Component/s: Replication
    • None
    • Replication
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, we only write down oplog entries for in progress transactions if they are prepared. We have a few invariants in transaction_participant.cpp that make sure we do not set the oldest oplog entry timestamp if the transaction is not prepared.

      This behavior changes once we allow multiple oplog entries per transaction, so we should remove those invariants for PM-1035.

            Assignee:
            [DO NOT USE] Backlog - Replication Team
            Reporter:
            Pavithra Vetriselvan
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: