On this page本页内容
Before you attempt any downgrade, familiarize yourself with the content of this document.
Before you upgrade or downgrade a replica set, ensure all replica set members are running. If you do not, the upgrade or downgrade will not complete until all members are started.
Once upgraded to 5.0, if you need to downgrade, we recommend downgrading to the latest patch release of 4.4.
Optional but Recommended. Create a backup of your database.
If your deployment has access control enabled, your downgrade user privileges must include privileges to list and manage indexes across databases. A user with root role has the required privileges.
To downgrade from 5.0 to 4.4, you must remove incompatible features that are persisted and/or update incompatible configuration settings. These include:
MongoDB 5.0 changed the default value for cluster-wide read and write concerns, and downgrading to MongoDB 4.4 might change those defaults back. Consider manually configuring your cluster's default read and write concern before downgrading:
setDefaultRWConcern command."Majority" read concern to prevent cache pressure in certain situations, you may want to configure --enableMajorityReadConcern false or replication.enableMajorityReadConcern: false once you downgrade.. or $ CharactersMongoDB 5.0 adds support for including the . or $ characters in document field names. You must delete any documents containing field names that include the . or $ characters before downgrading to MongoDB 4.4.
MongoDB 5.0 enables support for slim-format timezone data files. If using slim-format timezone data files in your deployment, as provided to MongoDB with the --timeZoneInfo command line option or processManagement.timeZoneInfo configuration file setting, you must downgrade to MongoDB 4.4.7 or later, or else revert your timezone data files to use the previous non-slim-format data files.
To downgrade the featureCompatibilityVersion of your standalone:
mongo shell to the mongod instance.featureCompatibilityVersion to "4.4".db.adminCommand({setFeatureCompatibilityVersion: "4.4"})
The setFeatureCompatibilityVersion command performs writes to an internal system collection and is idempotent. If for any reason the command does not complete successfully, retry the command on the mongod instance.The following steps are necessary only if fCV has ever been set to "5.0".
Remove all persisted 5.0 features that are incompatible with 4.4. These include:
auditLog.runtimeConfiguration to false in the node's configuration file.Remove all persisted features that use 5.0 features. These include but are not limited to:
$dateAdd or $sampleRate, they must be removed. See New Aggregation Operators for the full list.Before proceeding with the downgrade procedure, ensure that the prerequisites have been completed.
Using either a package manager or a manual download, get the latest release in the 4.4 series. If using a package manager, add a new repository for the 4.4 binaries, then perform the actual downgrade process.
Before you upgrade or downgrade a replica set, ensure all replica set members are running. If you do not, the upgrade or downgrade will not complete until all members are started.
Once upgraded to 5.0, if you need to downgrade, we recommend downgrading to the latest patch release of 4.4.
mongod instance.To cleanly shut down the mongod process, connect mongosh to the instance and run:
db.adminCommand( { shutdown: 1 } )
A clean shutdown of a mongod completes all pending operations, flushes all data to data files, and closes all data files.
Disable any configurable 5.0 features by updating the mongod instance's configuration file before restarting.
mongod instance.Replace the 5.0 binary with the downloaded 4.4
mongod binary and restart.