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

Upgrade to v6.2 fails if a collection with recordPreImages exists

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 6.0.4
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • Hide
      m 6.0.4
      mlaunch init --replicaset --nodes 1
      mongo
      > use test 
      > db.coll1.insert({ _id: 1, created_at: new Date() });
      > db.runCommand({ collMod: "coll1", recordPreImages: true });
      > db.getSiblingDB("admin").shutdownServer()
      
      # This will fail
      rapid/mongodb-macos-x86_64-6.2.0/bin/mongod --replSet replset --dbpath data/replset/rs1/db --logpath data/replset/rs1/mongod.log --port 27017 --wiredTCacheSizeGB 1 
      
      Show
      m 6.0.4 mlaunch init --replicaset --nodes 1 mongo > use test > db.coll1.insert({ _id: 1, created_at: new Date() }); > db.runCommand({ collMod: "coll1" , recordPreImages: true }); > db.getSiblingDB( "admin" ).shutdownServer() # This will fail rapid/mongodb-macos-x86_64-6.2.0/bin/mongod --replSet replset --dbpath data/replset/rs1/db --logpath data/replset/rs1/mongod.log --port 27017 --wiredTCacheSizeGB 1
    • QE 2023-02-20, QE 2023-03-06

      This is an outcome of SERVER-60919 where recordPreImages was removed in favour of changeStreamPreAndPostImages.

      MongoDB v6.2 will fail to start in an upgrade scenario if there is a collection with recordPreImages option.

      This issue manifests if the upgrade source has FCV set to "6.0" or "6.1"

            Assignee:
            mindaugas.malinauskas@mongodb.com Mindaugas Malinauskas
            Reporter:
            dmitry.ryabtsev@mongodb.com Dmitry Ryabtsev
            Votes:
            1 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: