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

Log time spent waiting for read concern

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication

      This is a request similar to SERVER-18067.

      At present the only way to infer if a query might have waited for read concern is by checking for the lag at the time of query execution. This is not straightforward and can still be inconclusive, especially if the query execution time & lag are under 1 second (i.e. t2 resolution is limited to 1s).

      Would be nice to have the time spent by a query waiting for read concern as a separate item in the log message.

            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
            10 Vote for this issue
            17 Start watching this issue