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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Critical - P2
    • Resolution: Fixed
    • Affects Version/s: 4.0.5, 4.0.9
    • Fix Version/s: 4.0.10
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      Execution Team 2019-06-03
    • Case:

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                13 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: