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

Use LockerImpl for the startup code path instead of LockerNoop

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Storage
    • Storage Execution

    Description

      SERVER-26879 proposes getting rid of LockerNoop and de-virtualizing the Locker class.
      SERVER-35970 proposes a similar task to this ticket in the comments; and in the description it proposes a 3rd Locker implementation for startup.

      OperationContextNoop should be looked into as well. The only place it appears to be used in production is the StorageEngineImpl constructor, otherwise just testing.

      SERVER-35970 alludes to the lock manager needing to be initialized earlier during startup in order for the storage engine initialization to use LockerImpls. I have not investigated whether this would be difficult, but there is no known impediment.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              dianna.hohensee@mongodb.com Dianna Hohensee
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: