Reference: https://www.mongodb.com/docs/manual/release-notes/3.4-upgrade-standalone/
My mongodb systems are running under CentOS-7 and their only clients are Java apps which pull from v3.2.8 AND also v3.4.6 MongoDB databases. The MongoDB servers are AWS EC2s and are NOT clustered.
Is it really as simple as this:
- Stop MongoDB
systemctl stop mongodb.service - Replace existing 3.2 binaries with 3.4 binaries
sudo su -
mv /App/mongodb/bin /App/mongodb/bin3.2.8
cp -pr /App/mongodb/bin3.4.6 /App/mongodb/bin - Start MongoDB
systemctl start mongodb.service - Enable backwards-incompatible 3.4 features
/App/mongodb/bin/mongo --quiet --eval ‘db.adminCommand( { setFeatureCompatibilityVersion: “3.4” } )’
exit
Do I need to make any changes to the data or metadata for my data? Anything at all?
Should I stop my EC2s, snapshot the drive where MongoDB has all its data, and then start the EC2s and start up my MongoDB databases as a first step? I will if there is ANY chance I’ll need to backout the upgrade because something “goes wrong”.
Thanks.