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

LockerNoop::isW() always returns true allowing multiple operations think they are holding the global exclusive lock at the same time

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 5.0.4, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v5.0
    • Execution Team 2021-09-06
    • 137

      This is problematic because the profile command on mongos uses a LockerNoop and CollectionCatalog::write(). SERVER-58736 introduced an optimization to skip copying the collection catalog on write if the exclusive global lock is held. But the usage of LockerNoop in the profile command breaks this assumption given that isW() always returns true.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: