mongodb single instance running with --auth flag enabled so do i need to consider authtenication upgrade instructions?

16 views

Skip to first unread message

arun....@gmail.com

unread,

Feb 10, 2016, 9:19:42 PM2/10/16

to mongodb-user

Actually am upgrading 2.2.0 single instance of mongodb to 3.2 current version.
my mongodb single instance running with --auth flag enabled so while upgrading to 2.4 to 2.6 .. do I need to consider authentication and authorization specific instructions given in upgrade notes or can I just simply follow Upgrade Standalone mongod Instance to MongoD insturctions just copying the 2.6 binaries

Stephen Steneker

unread,

Feb 11, 2016, 3:29:35 PM2/11/16

to mongodb-user

On Thursday, 11 February 2016 13:19:42 UTC+11, arun.skumar wrote:

Actually am upgrading 2.2.0 single instance of mongodb to 3.2 current version.

my mongodb single instance running with —auth flag enabled so while upgrading to 2.4 to 2.6 .. do I need to consider authentication and authorization specific instructions given in upgrade notes or can I just simply follow Upgrade Standalone mongod Instance to MongoD insturctions just copying the 2.6 binaries

Hi Arun,

Please follow the authentication schema upgrades and other procedures as documented in the relevant version upgrade instructions. The documented procedures are the only supported (and tested) upgrade path.

Upgrade steps for authentication schema changes are particularly essential, but skipping any required steps or versions on the upgrade path is very likely to cause issues with your deployment.

You should also take a backup before each major version upgrade. If something goes awry in your upgrade process or some required steps have been skipped, you will then have the option of restoring a previous known-good deployment.