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

Ignore oplog timeout in serverStatus opLatencies

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Minor - P4
    • Resolution: Duplicate
    • 3.4.15
    • None
    • Diagnostics, Querying
    • None
    • Query 2018-06-18

    Description

      The opLatencies section of serverStatus was added in MongoDB 3.4. These metrics are collected by FTDC, Ops Manager/Cloud Manager monitoring, and third party tools.

      On an idle replica set, read latencies can be observed in the 5000ms range due to replication timeout.

      This is confusing for anyone observing these metrics and they may believe there is a performance problem, solely based on these artifacts. When a steady write load is applied, these metrics even out.

      Splitting oplog latencies out from this metric would prevent this confusion, but still allow diagnosis of replication issues.

      Attachments

        Issue Links

          Activity

            People

              david.storch@mongodb.com David Storch
              kevin.arhelger@mongodb.com Kevin Arhelger
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: