Allow secondaries to see “abort” oplog entry on non-existent transactions

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.1.9
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2019-02-25
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For large transacations, if a transaction has written any oplog entry, “abort” must write a corresponding oplog entry. We don't need to write an abort oplog entry if the transaction hasn't written anything, but we may do it sometimes out of convenience and this must be safe. Thus secondaries should be ready to see abort oplog entries for non-existent transactions.

            Assignee:
            Jason Chan
            Reporter:
            Siyuan Zhou
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: