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

Background validation hook checks wrong serverStatus parameter

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.3.1
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2019-11-18

      We're currently checking the wrong parameter from "serverStatus" to see if checkpoint cursors are supported by a storage engine. This prevents the background validation hook from running at all.

       Here, we check for

      !conn.adminCommand("serverStatus").storageEngine.supportsCheckpoints

      when we should be checking for

      !conn.adminCommand("serverStatus").storageEngine.supportsCheckpointCursors

       

      Currently, running this with the WiredTiger we see this:

      Skipping background validation against test node: localhost:20000 because its storage engine does not support background validation (checkpoints).

       

      Logging the "serverStatus.storageEngine" we have these options:

      {
       "name" : "wiredTiger",
       "supportsCommittedReads" : true,
       "oldestRequiredTimestampForCrashRecovery" : Timestamp(1572447953, 4),
       "supportsPendingDrops" : true,
       "dropPendingIdents" : NumberLong(0),
       "supportsSnapshotReadConcern" : true,
       "supportsCheckpointCursors" : true,
       "readOnly" : false,
       "persistent" : true,
       "backupCursorOpen" : false
       }

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: