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

Set CurOp nss and opDescription within same client lock

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0, 8.0.0-rc5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Service Arch
    • Fully Compatible
    • v8.0
    • Service Arch 2024-04-29, Service Arch 2024-05-13
    • 35

      The service entry point set properties of one CurOp in different locks. When executing aggregate with "$currentOp", it is possible that mongod can get an incomplete CurOp object in which some properties are not set yet, for example, CurrOp::_opDescription has been set while the CurrOp::_nss is missed. 

      In this ticket, we should make service entry point always set the CurOp nss and opDescription within same client lock.

            sophia.tan@mongodb.com Sophia Tan
            sophia.tan@mongodb.com Sophia Tan
            0 Vote for this issue
            3 Start watching this issue