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

Authorization User Cache should be able to hold select users in memory

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.1.4
    • Admin
    • None
    • Fully Compatible
    • Security 2018-09-10, Security 2018-09-24, Security 2018-10-08
    • 19

    Description

      Currently, updating any user will invalidate its entry in the user cache. The next time that user attempts to perform an operation, the AuthorizationManager will pull the canonical document from disk, taking a shared lock on the system's user collection. If a long running operation has taken an exclusive lock on the whole system, the AuthorizationManager may block until it finishes. Attempting to run administrative operations such as killOp or currentOp may cause the AuthorizationManager to perform this update.

      We should have a mechanism to ensure that at least some users are always held in memory. Authentication or authorization, and by extension running killOp, would never need to block.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35637 DDL operations blocked by transactions also block authentication

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

          Task - A task that needs to be done. SERVER-13586 Remove user cache invalidation from user management commands

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-33648 Attempting to perform user- and role-management commands in db.eval() with nolock=false can lead to deadlock

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-35890 Make Authorization user cache a general purpose lifetime manager

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

          Activity

            People

              jonathan.reams@mongodb.com Jonathan Reams
              spencer.jackson@mongodb.com Spencer Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: