I am updating several Meteor apps from v188.8.131.52 to 184.108.40.206.
I am a little confused as to whether the Mongo DB was automatically upgraded in the process.
I took a development version at v220.127.116.11, then progressively updated it to 18.104.22.168, 1.4, 1.5, then 22.214.171.124. The only special step I had to do was 'meteor npm install --save babel_runtime after going to 1.5.
The result runs fine. When I do Meteor Mongo from a different linux shell it shows Mongo Shell 3.2.15. Does this mean the MongoDB is running Mongo 3.2 now and the DB has been upgraded as well?
I have done this for 4 apps. Is it now recommended I convert to wiredTiger for each app?
I have found instructions on how to change the storageengine to wiredtiger for my development dbs, and have decided not to do that yet. I may do that for deployed dbs, though.
As for my deployed apps, all the dbs from the various METEOR apps are accessible from a single mongo command. I have yet to find any description of whether my dbs will work fine if I upgrade a single app to 3.2 but leave the other apps at 2.6. My instinct tells me I may need to migrate all my apps that use that mongo instance to 3.2 at the same time.