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

Extend diagnostic logging on tassert failure to dump contents of CurOp/OpDebug

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • Fully Compatible
    • v8.0, v7.0
    • QO 2024-08-05, QO 2024-08-19
    • 200

      The work SERVER-90282 makes it so that when a tassert() failure occurs during a find command, the command that was running at the time of failure is logged. We should extend this mechanism to also log other basic facts about the operation, in particular those that are available from CurOp and OpDebug.

      I think CurOp / OpDebug is probably small enough that we don't have to worry about logging these extra diagnostics on every tassert failure (in case there is a bug that causes the tassert rate to spike).

            Assignee:
            henri.nikku@mongodb.com Henri Nikku
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: