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

Oldest timestamp not always advanced with --enableMajorityReadConcern=false, on secondary nodes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Critical - P2 Critical - P2
    • 4.0.10
    • Affects Version/s: 4.0.5, 4.0.9
    • Component/s: Storage
    • Labels:
      None
    • Fully Compatible
    • ALL
    • Execution Team 2019-06-03

      Run the following against a replica set with majority read concern disabled. It generates bursts of updates spaced 15 seconds apart.

      function update() {
          for (var i = 0; i < 1000; i++)
              db.c.insert({x: 0})
          for (var x = 0; ; x++) {
              db.c.updateMany({}, {$set: {x: x}})
              if (x%20 == 1)
                  sleep(15000)
          }
      }
      

      FTDC shows the following:

      During the bursts we are executing a couple hundred batches per second, but the oldest timestamp is not advanced on every batch, and in fact may not be advanced for minutes at a time. This can cause a large amount of data to be pinned in cache.

        1. oldest.png
          144 kB
          Bruce Lucas

            Assignee:
            milkie@mongodb.com Eric Milkie
            Reporter:
            bruce.lucas@mongodb.com Bruce Lucas (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            14 Start watching this issue

              Created:
              Updated:
              Resolved: