Track oplog fetch metrics during initial sync in replSetGetStatus and FTDC

XMLWordPrintableJSON

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

      In InitialSyncer::_enqueueDocuments() there is a TODO (line 2256) to update metrics with OplogFetcher::DocumentsInfo. This struct carries per-batch counts for networkDocumentCountnetworkDocumentBytestoApplyDocumentCount, and toApplyDocumentBytes.

      Currently there is no visibility into oplog fetch throughput during initial sync. Adding running totals for these fields to InitialSyncSummaryStats would expose them via replSetGetStatus and FTDC, enabling diagnosis of slow initial syncs where the bottleneck is in the oplog fetch/apply phase rather than data cloning.

            Assignee:
            Unassigned
            Reporter:
            Denis Trailin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: