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

Make a new lock helper to encapsulate DBLock and CollectionLock usage

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Storage
    • Storage Execution

    Description

      Lock-free reads makes it so that sharding refresh logic cannot use AutoGetDb or AutoGetCollection helpers because those helpers would throw stale config errors, which would stop the refresh operation to fix the staleness.

      There are a number of cases already where code takes DBLock followed by CollectionLock, to avoid the additional logic run in the AutoGet* helpers. We could make a new wrapper for these operations, a 'dumb' wrapper as opposed to the 'smart' AutoGet* wrappers.

      Attachments

        Activity

          People

            backlog-server-execution Backlog - Storage Execution Team
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: