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

Make readConcern:local wait for write concern on a read-only transaction

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0-rc0
    • Component/s: Replication
    • Labels:
      None

      Description

      A transaction started with readConcern:local that doesn't do any writes does not need to wait for the data it read to be committed when the transaction commits.  SERVER-34038 implemented the behavior that causes read-only txns with RC 'majority' and 'snapshot' to wait for the data read to be committed at commit time, and intentionally excluded RC 'local' from that waiting.  However, since SERVER-34837 isn't going to get done for 4.0, we should temporarily make RC 'local' behave like RC 'majority' and 'snapshot' in this case, so that the fact that the readConcern default is incorrect will not be observable.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              spencer Spencer Brody
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: