Plan & test MongoDB database migration from 2.x to 3.x

[jykae]

Meteor upgrade brought upgrade to MongoDB for new database engine. See MongoDB documentation for migration steps.

"Your development database is using mmapv1, the old, pre-MongoDB 3.0 database engine. You should consider upgrading to Wired Tiger, the new engine. The easiest way to do so in
development is to run meteor reset. If you'd like to migrate your database, please consult https://docs.mongodb.org/v3.0/release-notes/3.0-upgrade/"

In DEVELOPMENT, use meteor reset to switch to WiredTiger based

In PRODUCTION, follow the procedure by MongoDB docs.

GENERAL PROCEDURE https://docs.mongodb.com/v3.0/release-notes/3.0-upgrade/#general-action-procedure

• take database dump from old
• upgrade mongo
• restore data to upgraded mongo that uses WiredTiger

IMPORTANT:
"To change storage engine to WiredTiger, you will need to manually export and upload the data using mongodump and mongorestore"
https://docs.mongodb.com/v3.0/release-notes/3.0-upgrade/#change-storage-engine-to-wiredtiger
=> Old DB engine cannot read Wired Tiger data format.

Test procedure on staging/test server first.

[jykae]

Mongodump & restore with Docker, https://blog.studiointeract.com/mongodump-and-mongorestore-for-mongodb-in-a-docker-container-8ad0eb747c62#.vtvgxojzb

[jykae]

Successful procedure on my local virtualbox production environment.
Next step, do the same on nightly.apinf.io

[jykae]

Verify engine in mongo shell:

db.serverStatus().storageEngine

[jykae]

nightly.apinf.io upgraded to 3.2.6 and using wiredTiger

[jykae]

Reopened for need to test also deployments with new docker-compose based setup

[bajiat]

@jykae Should I co-assign @shaliko to this task?