Compose Updates - MongoDB and Elasticsearch

Over the last few weeks, we've been quietly releasing some minor updates for MongoDB and Elasticsearch. We're happy now to let people know about them and what's changed.

MongoDB 3.0.6

We've brought MongoDB version 3.0.6 online for anyone who wants to upgrade to it; updating is recommended for the many bug fixes that have accumulated in this release. It should be noted though that many of the headline fixes were actually related to the WiredTiger storage engine so didn't impact on current Compose deployments. That said, there's still plenty of fixes to benefit from in the 3.0.6 update.

To upgrade to 3.0.6 by selecting Settings and in the Change MongoDB Version selecting 3.0.6 then clicking Change Version. New MongoDB deployments will continue to be initially provisioned with MongoDB 2.6.9 but can be upgraded immediatly while new beta MongoDB+ deployments are already being provisioned with 3.0.6.

Elasticsearch 1.7.3

The Elasticsearch 1.7.3 update pulls in the many small changes from the 1.6 updates and the subsequent security updates of 1.7 (which were already mitigated on the Compose platform). Once we were happy there was a stable release available, we updated our available versions. New deployments are being created as 1.5.3, so remember to upgrade them when you create them.

Why older versions for new deployments?

As you may have noticed above, and as some users have asked, why we have a period of time where we have newer versions of databases available but provision databases with the older versions. There's two parts to the answer. The first is we want to ensure that customers can duplicate their existing deployments with as little intervention from us as possible, which means keeping older versions of databases around. The second part is, though, that we only allow users to move upwards in versions from the Compose console – moving downwards is usually a complex task best left to Compose support and only then after considering all the issues involved.

Anyway, because you can't go backwards through versions, the easiest way to make older database versions available in new deployments is to setup new database deployments with the oldest current version supported. The beta services, like MongoDB+, are moved to the latest version specifically because they are beta services and users should not have a version dependency they need to duplicate.