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

HMAC key refresh thread holds onto an OperationContext

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.0-rc3
    • Affects Version/s: 3.6.0-rc1
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Sharding 2017-11-13

      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.

            Assignee:
            randolph@mongodb.com Randolph Tan
            Reporter:
            daniel.gottlieb@mongodb.com Daniel Gottlieb (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: