Move CurOp code out of writeConflictRetry and other exception_utils

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • Storage Execution 2025-03-31, Storage Execution 2025-04-14
    • 200
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently track the number of write conflicts in curop.

      It is incremented from various calls in exception_util with 
      CurOp::get(opCtx)->debug().additiveMetrics.incrementWriteConflicts(1);
      We should consider storing this metric somewhere (outside of curop) that curop can check instead.

            Assignee:
            Ernesto Rodriguez Reina
            Reporter:
            Shin Yee Tan
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: