A quicker way to identify your MongoDB deployment and the latest update to MongoDB itself are detailed in this edition on Compose Notes, the small and important things which are happening on Compose.
MongoDB vs MongoDB Classic
We've been asked to make it easier to tell the difference between MongoDB and MongoDB Classic on Compose. But first...
A quick refresher: A MongoDB Classic deployment is our older, non-SSL, exposed replica set, minimalist variant of a MongoDB database; just two servers (and a hidden backup server) providing MongoDB services. Classic currently supports up to MongoDB 3.0.11.
MongoDB Classic has been superseded by MongoDB, our new MongoDB deployments. These use a replica set, enclosed in a single shard and fronted by MongoDB configuration and routing servers. Among other things, it supports the latest MongoDB 3.2.x and WiredTiger. It also lets us provide effective SSL and enhances the high availability capabilities of MongoDB. It's this MongoDB that we recommend to new users.
Now, in the deployments page in the Compose console we show MongoDB Classic deployments with a white icon like this:
and MongoDB deployments with a green icon like this:
But monitoring the support queue we noticed something; users with only one type of MongoDB couldn't see any indication there was another kind of deployment. So we've made a little change. When you go to a MongoDB Classic deployment now, you'll see this:
The words MongoDB Classic are now following the name of your deployment. This should make it clearer which kind of MongoDB deployment you are dealing with and which documentation you should be referring to - MongoDB or MongoDB Classic.
Talking about the latest MongoDB, MongoDB 3.2.8 is now available on Compose. According to MongoDB Inc, the 3.2.8 update addresses some WiredTiger issues. This includes problems with cache memory consumption under load and performance under load which, in combination with some hard to trigger race conditions, makes it especially recommended for MongoDB WiredTiger users.
You'll be prompted to update when you go to the Compose console for your MongoDB deployment:
Click on Settings either in that message or in the left hand sidebar and you'll see, at the top of the Settings page:
It should already be set to update you to the latest version. Remember that this will require a rolling restart on your MongoDB deployment. All you need to do is click Change Version and wait a minute or two while the update is applied. Now you'll be right up to date.