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

Invariant that secondary oplog application doesn't get prepare conflicts

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Fully Compatible
    • Repl 2023-07-24, Repl 2023-08-07, Repl 2023-08-21, Repl 2023-09-04, Repl 2023-09-18, Repl 2023-10-02
    • 135

      Alternatively, maybe we should crash the server if secondary oplog application repeatedly get write conflicts for some time as WiredTiger will map all the WT_PREPARE_CONFLICT errors to WT_ROLLBACK (aka write conflicts) for write operations.

      We may want to add the invariant / the crashing behavior only in testing, not in production.

            Assignee:
            jiawei.yang@mongodb.com Jiawei Yang
            Reporter:
            lingzhi.deng@mongodb.com Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: