Feature Summary and Revision History

Feature Description

This release provides support for MongoDB version 6.0

Upgrade, Migrate, and Backward Compatibility Considerations

• Supported DRA Releases for Upgrading to 6.0: You can upgrade vDRA 24.1.0 (mongoDB version,5.0) to vDRA 24.2.0 (mongoDB version, 6.0).

• Un Supported DRA Releases for Upgrading to 6.0: Any DRA version prior to DRA 24.1(mongo 5.0) like DRA 23.1/23.2(mongo 4.4), 22.2 (mongo 4.2) and previous versions of DRA doesn’t support direct upgrade to DRA 24.2(mongo version 6.0)

  Refer the link for upgrading the replica set to 6.0.

  Note	Upgrading to DRA 24.2 is supported only from DRA 24.1.0

Mongo Java Driver: Current DRA Version 24.2.0 supports mongo java driver 3.12.9.

The following are the common prerequisites for both upgrade and downgrade:

• Run the following CLI before upgrade:

  #database genericfcvcheck 5.0

  Note	Make sure to run the above CLI before upgrade and / or downgrade on all sites.

• Specify any one of the CLI options:

  • Set: This option checks and sets FCV only on primary.

    Note

    We recommend using the Set option first and then Check to make sure that FCV is replicated on primary members. Upgrade/downgrade should not be triggered if any error is found in the above CLI or FCV is not replicated on secondary members. Make sure to resolve the CLI error, rerun the CLI, and then only proceed for upgrade or downgrade.

  • Check: This option only checks FCV on all members (primary, secondary, and arbiter).

• Run the following CLI before upgrade:

  #database dwccheck

  Note	CLI automatically takes care of the defaultWriteConcern version on all databases.

• Specify any one of the CLI options:

  • Set: This option checks and sets dwc on primary members.

    Note

    We recommend using the Set option first and then Check to make sure that DWC is replicated on primary members. Upgrade/downgrade should not be triggered if any error is found in the above CLI or DWC is not replicated on secondary members. Make sure to resolve the CLI error, rerun the CLI, and then only proceed for upgrade or downgrade.

  • Check: This option only checks dwc on all members.

  • (set/check) << set

    • Set: This option checks and sets defaultWriteConcern.

    • Check: This option only checks defaultWriteConcern on all members(primary/secondary).

Deprecated Mongo Commands and Parameters

• From 24.2.0, the mongo command is replaced with mongosh command. Refer the following mongosh command usage example:

  root@mongo-s105:/# mongosh --port 27033
  
  Using MongoDB: 6.0.15
  Using Mongosh: 1.10.6
  orchestrator[primary] test>

• The following parameters are renamed in MongoDB 6.0:

  Previous Name	New Name
  wiredTigerConcurrentReadTransactions	storageEngineConcurrentReadTransactions
  wiredTigerConcurrentWriteTransactions	storageEngineConcurrentWriteTransactions

Upgrade to 24.2.0

1. Run the prerequisite steps.

2. Follow the standard documented procedure for upgrade.

Downgrade from 24.2.0

1. Run the steps mentioned in the prerequisite section.

2. Follow the standard documented procedure for downgrade.

Feature Summary and Revision History

Revision History

Feature Description

In CPS 24.2.0 release, Alma Linux version 8.8 is replaced with Alma Linux 8.9 along with upgrading to the latest rpm packages and their dependencies.

With Alma Linux 8.9 the kernel version is modified to:

# rpm -qa | grep kernel-[0-9]
kernel-4.18.0-513.24.1.el8_9.x86_64

# cat /etc/redhat-release
AlmaLinux release 8.9 (Midnight Oncilla)

# uname -a
Linux localhost.localdomain 4.18.0-513.24.1.el8_9.x86_64 #1 SMP Thu Aug 8 11:23:13 EDT 2024 x86_64 x86_64 x86_64 GNU/Linux

Feature Summary and Revision History

Feature Description

This release provides support for MongoDB version 6.0.

Following are the supported and unsupported CPS releases:

• Supported CPS Releases for upgrading to 6.0:

  You can upgrade CPS 24.1.0 (using mongoDB version 5.0.20) to CPS 24.2.0 (using mongoDB version 6.0.14). Upgrade to MongoDB 6.0 is supported only from MongoDB 5.0. For example, if you are running a 4.4 series, you must first upgrade to 5.0 before you can upgrade to 6.0.

  Important

  Upgrading to CPS 24.2 is supported only from CPS 24.1.

• Un Supported CPS Releases for upgrading to 6.0:

  Any CPS versions prior to CPS 24.1 (using MongoDB version 5.0.20) such as CPS 23.1 or 23.2 (using MongoDB version 4.4.18), CPS 22.2 (using MongoDB version 4.2.20), or CPS 22.1.1 (using MongoDB version 4.0.27), CPS 21.1 (using MongoDB version 3.6.9), or CPS 19.4/18.2 (using MongoDB version 3.4.5), and previous versions of CPS does not support direct upgrade to CPS 24.2 (using MongoDB version 6.0).

  To upgrade the Replica set to 6.0, go to https://www.mongodb.com/docs/manual/release-notes/6.0-upgrade-replica-set/

The compatible Java driver for 6.0 is 3.12.9.

The following parameters are renamed in MongoDB 6.0:

Prerequisite for Upgrading from 24.1.0 to 24.2.0

While performing In-Service Software Migration (ISSM) from 24.1.0 to 24.2.0, after bringing up the new Cluman with 24.2.0, verify whether the DefaultRWConcern configuration for MongoDB is set to 1 using the diagnostics.sh script

Note	In CPS 24.2.0, the diagnostics.sh script has been updated to verify whether the DefaultRWConcern configuration for MongoDB is set to 1.

• If the value is already set to 1, the diagnotics.sh script will report the DefaultRWConcern check as PASS, where NO action is required from the user.

  
  [root@cluman ~]# diagnostics.sh --get_r
  CPS Diagnostics HA Multi-Node Environment
  ---------------------------
  Checking DefaultRWConcern for the MongoReplicaSet Members...[PASS]
  Checking replica sets...
  

• If the value is not set to 1, the diagnotics.sh script will report the DefaultRWConcern check as FAIL, and the user should run the following script from Cluman to update the value to 1.

  
  [root@localhost ~]# diagnostics.sh --get_r
  CPS Diagnostics HA Multi-Node Environment
  ---------------------------
  Checking DefaultRWConcern for the MongoReplicaSet Members...
  sessionmgr02:27727 is not having the right DefaultRWConcern...[FAIL]
  sessionmgr02:27737 is not having the right DefaultRWConcern...[FAIL]
  Checking replica sets...
  
  source /var/qps/install/current/scripts/bin/support/mongo/dbcmds.sh
  
  replica_sets=$(perl -wlne 'print if /SETNAME=/../MEMBER1=/;'/etc/broadhop/mongoConfig.cfg |awk -F= /MEMBER1/'{print $2}')
    for set in ${replica_sets[*]}; do
     echo $set;
     x="$MONGO_ADMIN  ${set}   --eval 'db.adminCommand(  {setDefaultRWConcern : 1,           \"defaultWriteConcern\": { \"w\" : 1 ,\"wtimeout\" : 0  } })'";
     xx=$(eval $x);
     echo $xx
  done
  

Note	This prerequisite is not applicable for fresh installation.