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

HMAC key refresh thread holds onto an OperationContext

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 3.6.0-rc1
    • Fix Version/s: 3.6.0-rc3
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Sharding 2017-11-13

      Description

      The default key refresh time is 3 months: https://github.com/mongodb/mongo/blob/master/src/mongo/db/keys_collection_manager.cpp#L37

      There's a background thread responsible for refreshing keys. That thread renews its OperationContext on each iteration. However, an iteration (I believe) can sleep for the full three months when newly negotiated keys are set to expire. Holding this OperationContext open can block WT tables from being dropped. Generally speaking, an OperationContext should be short-lived.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31573 WT table not dropped on primary after collection is dropped

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31101 WT table not dropped after collection is dropped due to long-running OperationContext

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

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                10 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: