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

Get rid of LockerNoop and devirtualize Locker

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Blocked
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Concurrency, Internal Code
    • Storage Execution

    Description

      Now that the real LockManager and LockState are usable in unittests we should remove the fake LockerNoop. This is related to the work to merge OperationContext/Impl/Noop into a single concrete type.

      Attachments

        Issue Links

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-42901 Use LockerImpl for the startup code path instead of LockerNoop

          • Major - P3 - Major loss of function.
          • Backlog

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-60229 lock manager for mongos

          • Major - P3 - Major loss of function.
          • Backlog
          is related to

          Task - A task that needs to be done. SERVER-35970 Use regular Locker during storage engine initialization

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-31247 enhance LockerNoOp

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              mathias@mongodb.com Mathias Stearn
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated: