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

Replaying prepared transaction writes for commit oplog entry during replication recovery and initial sync should set commit and durable timestamp for those writes.

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.10
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Repl 2019-03-11, Repl 2019-03-25, Repl 2019-04-08

      Currently, when we commit a prepared transaction as a part of commit oplog replay, we don't set any timestamp (commit & durable timestamp) to the wiredTiger transaction via recovery unit. So, basically we are committing the write operations as non-timestamped. This would cause problem for data visibility and durability.

            Assignee:
            suganthi.mani@mongodb.com Suganthi Mani
            Reporter:
            suganthi.mani@mongodb.com Suganthi Mani
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: