Closed davidzwa closed 2 years ago
https://www.mongodb.com/docs/manual/reference/command/setFeatureCompatibilityVersion/ Thinking of something like this combined with an update/pre-upgrade validation script. This 'feature compatibility' thing is something outside our control once the mongo service crashes, so as a choco user we are forced to roll back to 5.2
Setting the featureCompability to 5.2 allowed me to upgrade to 5.3 without the service crashing
I started up MongoSh in MongoDb Compass:
db.adminCommand( {
setFeatureCompatibilityVersion: "5.2",
writeConcern: { wtimeout: <timeout> }
} )
Resulted in this output when querying:
Lets hope this doesnt happen more in the future
Expected Behavior
I expect mongo/mongod to start the service without stopping.
Current Behavior
The service stops immediately with the log message mentioning the
featureCompatibilityVersion
is set to 5.1 in the admin table. (Im slowly typing this issue and realizing this might have little to do with the choco package... still maybe we can think of a fix which does not involve removing the admin table)Steps to Reproduce (for bugs)
choco install mongodb
(-y globally enabled)Mongo log
TL;DR
Are we not running 5.3?
Full log:
Context
Updated to 5.3.1 and reverted to 5.2 to make the db working again.
Proof that the config file exists:
Service execution command:
Your Environment