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

Report the WT all_durable timestamp in serverStatus

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution

      It may be helpful to report the "no holes" point for debug-ability. For example for flow control, where replication could be held up by an oplog hole or because of throttling.

      Note: replSetGetStatus already returns the last durable optime and walltime. Primaries periodically update last durable with the WT all_durable point, via the journal flushing logic. Secondaries, however, do not periodically fetch the WT all_durable timestamp. I'm envisioning either: the serverStatus section reports differently for primary mode vs secondary mode, taking advantage of the journal flushing lookups; or both primary and secondary mode fetch from the storage engine directly (not sure whether there's a perf consequence to doing so).

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            dianna.hohensee@mongodb.com Dianna Hohensee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: