I was upgrading an app deployed with meteor-up to Meteor 2.12.0 and got an issue with the deployment connecting to the embedded standalone MongoDB 4.4 instance (ECONNREFUSED and ReplicaSetNoPrimary). Had to upgrade to MongoDB 5.0 (still standalone). Is this expected?
Cannot remember any requirements jumping from MongoDB 4.x to 5.x. But here is the changelog for the upgrade of MongoDB
Yeah, it seems to be compatible. I jumped from 2.5.6 to 2.12.0 in prod when it happened.
1 Like
We’re using 4.4, no issues. EOL approaching though so we need to move to 5 soon-ish.