Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12270

Docs for SERVER-37910: Create new serverStatus metric for number of operations applied on a secondary that's incremented at batch boundaries

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.7, 4.0.6, 3.6.11
    • Component/s: manual, Server
    • Labels:
      None

      Description

      Description

      Description:

      Added a new serverStatus metric named "repl.apply.batchSize" (https://docs.mongodb.com/manual/reference/command/serverStatus/#serverstatus.metrics.repl).

      Description:
      metrics.repl.apply.batchSize - The total number of oplog operations applied incremented at the oplog application batch boundaries whereas metrics.repl.apply.ops gets incremented after every operation.

      Engineering Ticket Description:

      repl.apply.ops is incremented for every op rather than at batch boundaries for the size of the entire batch so it's difficult to get a sense of the size of each batch. (https://docs.mongodb.com/manual/reference/command/serverStatus/#serverstatus.metrics.repl.apply.ops)

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Githook User
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 46 weeks, 2 days ago
                Date of 1st Reply: