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

Stop upconverting readConcern to snapshot internally for transactions

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2019-06-17, Repl 2019-07-01, Repl 2019-07-15, Repl 2019-07-29, Repl 2019-08-12, Repl 2019-08-26, Repl 2019-09-09
    • 0

      Initially, we planned that all multi-document transactions would run at readConcern level snapshot. However, over time the behavior for different readConcern levels within transactions has changed, and we have needed to check the original readConcern level to make decisions, such as what read source to use. It no longer seems to improve simplicity or readability of the code to internally upconvert the readConcern level to snapshot, and it has led to bugs, such asĀ SERVER-40123.

            Assignee:
            samy.lanka@mongodb.com Samyukta Lanka
            Reporter:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: