Get rid of the Locker implementation for MongoS

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • Sharding EMEA 2023-05-29
    • 55
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      It is unnecessary for MongoS to be acquiring locks in the first place, but there are some code paths that are shared between MongoD and MongoS which require this. However it shouldn't be necessary to have two different locker implementations between the two services.

              Assignee:
              Kaloian Manassiev
              Reporter:
              Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: