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

WiredTigerStats reported in curOp can accumulate from previous operations in bulk writes

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 5.0.25
    • Component/s: None
    • Storage Execution
    • ALL
    • Execution Team 2024-06-24, Execution Team 2024-07-22, Execution Team 2024-09-30, Execution Team 2024-10-14, Execution Team 2024-10-28, Execution Team 2024-12-09, Execution Team 2024-12-23, Execution Team 2025-01-06, Execution Team 2025-02-17, Storage Execution 2025-03-03, Storage Execution 2025-03-17, Storage Execution 2025-03-31
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We set the storage stats that we want to report in curop here with the assumption that computeOperationStatisticsSinceLastCall() is called at the end of every operation. However, it is possible not to meet these conditions ( + this on previous versions) resulting in some operations not calling computeOperationStatisticsSinceLastCall(). When we eventually do call the method on a slow op we want to log, _sessionStatsAfterLastOperation can be stale and we end up reporting storage stats that include prior operations.

            Assignee:
            ernesto.rodriguez@mongodb.com Ernesto Rodriguez Reina
            Reporter:
            shinyee.tan@mongodb.com Shin Yee Tan
            Votes:
            2 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None