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

Use WUOW in write ops under global write lock

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • Fully Compatible
    • Execution Team 2021-12-13, Execution Team 2022-02-21, Execution Team 2022-03-07, Execution Team 2022-03-21, Execution Team 2022-04-04, Execution Team 2022-04-18

      While not necessary for correctness as there can't be any concurrency going on it would be a nice cleanup to not have multiple modes that we need to support throughout the code base.

      For example, the collection catalog exposes a way to bypass the copy-on-write system to do collection modifications directly on the instances installed in the catalog (the inplace mode). Having modes like this is prone to error and misuse so it would be better if there was a single way to do these kind of writes.

            Assignee:
            henrik.edin@mongodb.com Henrik Edin
            Reporter:
            henrik.edin@mongodb.com Henrik Edin
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: