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

repl.apply.batches.totalMillis does not record the time spent applying batches

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • v3.6, v3.4
    • Storage 2018-01-01, Repl 2018-01-15, Repl 2018-01-29, Repl 2018-02-12, Repl 2018-02-26

    Description

      This behavior was observed in 3.4.4 (at least). The reason is that TimerHolder is declared here in applyOps, but applyOps doesn't wait for the batch to finish. This can be solved by moving TimerHolder to this block which does wait for the batch to finish. This would need to be done at each place where applyOps is called.

      This makes it difficult to determine whether the node is under heavy replication load and to diagnose issues related to that.

      Attachments

        Issue Links

          Activity

            People

              vesselina.ratcheva@mongodb.com Vesselina Ratcheva
              bruce.lucas@mongodb.com Bruce Lucas
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: