Sorry for the newbie question, but my fear for updating my Mlab Mongo Database from mongod version: 3.0.12 (MMAPv1 Engine) to latest mongodb 3.6 (WiredTiger Engine) is still holding me from make the leap to latest Meteor 1.6 and 1.7 versions.
This is a running application and I can’t afford to loose data in the process nor hold users from connecting to it for much long.
What are the steps and best practices? For local development it is just a question of reseting the database. I can’t do this on the production app. I know this may sound stupid, but updating meteor on Galaxy would NOT automatically update mongodb version on Mlab, right? What are the manual steps I should follow?