MongoDB

Managed instance of MongoDB. There’s a role for each supported major version, currently:

  • mongodb32

  • mongodb34

  • mongodb36

  • mongodb40

3.2 and 3.4 are end-of-life and should be upgraded.

Configuration

MongoDB works out-of-the box without configuration. You can put additional configuration in /etc/local/mongodb/mongodb.yaml. It will be joined with the basic config.

Command Line Interface

You can use the mongo Shell to query and update data as well as perform administrative operations.

Upgrade

Warning

Upgrade paths must include all major versions: 3.2 -> 3.4 -> 3.6 -> 4.0. Before each upgrade step, the feature compatibility version must be set to the current running mongodb version.

Set the compatibility version in the mongo Shell, for example:

db.adminCommand( { setFeatureCompatibilityVersion: "3.6" } )

To upgrade, disable the current role and enable the role for the next major version. MongoDB will be upgraded and restarted on the next management task run. This happens automatically after some time. You can trigger a rebuild with sudo fc-manage --build --directory immediately.

The restart will fail if the feature compatibility version is too old (“error 62”). To fix this, go back to the last working role version, rebuild, and set the version.

Monitoring

Our monitoring checks that the mongodb daemon is running.