Capture index build blocking replication metrics

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • v8.2, v8.0, v7.0
    • Storage Execution 2025-12-8, Storage Execution 2025-12-22
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We want to capture metrics related to the availability impact of replicated index builds, specifically the problem described by SERVER-112315.

      We should expose two serverStatus metrics:

      • The last amount of spent between receiving a commitIndexBuild oplog entry and an index build being committed. This should be captured in any replication state (either secondary or startup recovery).
      • The last amount of time spent between voting for commit (as self) and actually committing.

      This will tell us how long a node was blocking replication by building indexes.

            Assignee:
            Damian Wasilewicz
            Reporter:
            Louis Williams
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: