Child pages
  • Uprading to MongoDB 3.2 Using Wired Tiger
Skip to end of metadata
Go to start of metadata


OMK customers may wish to upgrade MongoDB to 3.2 and realize the efficiencies of Wired Tiger.  This example uses CentOS because this is the prevailing Linux distribution used by our customer base.


  • Ensure MondgoDB Authentication Is Set Correctly
  • Stop Running Services
  • Backup Current Database
  • Install MongoDB 3.2
  • Provision MongoDB 3.2
  • Restart OMK Services and Test


Ensure MongoDB Authentication Is Set Correctly

In order to ensure a smooth transistion ensure MongoDB authentication is set correctly.  The following script will facilitate this.

Stop Running OMK Services



Backup Current Database

Create Backup Directory

Dump MongoDB

Stop MongoDB


Install MongoDB 3.2

Update MongoDB Repository File

In order to install Mondgo3.2 edit /etc/yum.repos.d/mongod-org.repo to reflect the correct version. 


Install MongoDB 3.2 with yum

Provision MongoDB 3.2

Check what kinds of MongoDB configuration files are in /etc

If there is one called mongodb.conf it is no longer necessary.  Please move this to /root to avoid any future confusion. 

Make a backup of the old mondgod.conf and copy the new rpm version over it.

Provision MongoDB

Now make the following changes to mongod.conf

  • Change the dbPath to /data/mongodb
  • Provision wiredTiger (uncomment)

Delete temporary files associated with MongoDB

Remove any files in /tmp that look be be associated with MongoDB

If there is a file in /var/run/mongodb, then remove it.

Delete the contents of /data/mongodb and verify the group and owner of /data/mongodb is mongod.

Start MongoDB Service

Restore The Database

Setup MongoDB for OMK Applicatons

Restart OMK Services and Test

Restart Services


Log into each OMK Application via the GUI and verify the data is still there.  If everything is as it should be then delete /data/mongodump


  • No labels