Version upgrades of Sandbox and Shared plan databases starting Sept. 27, 2016

Notification of scheduled maintenance

An email notification with subject of “[ACTION REQUIRED] Version upgrades of Sandbox and Shared plan databases starting September 27” was sent on July 19, 2016 to the Technical Contact of accounts which have deployments that will be impacted by this scheduled maintenance. Reminders were sent out after that.

Key details

MongoDB 3.2 is now generally available on mLab, so we are in the process of making MongoDB 3.2 the default release version for all newly provisioned deployments. We are also taking steps to discontinue our support for MongoDB 2.6.

To this end, on Tuesday, September 27 we will start a four-day maintenance window to:

What and when

Prerequisites

How to avoid this maintenance window

If our planned maintenance window does not work well with your schedule, you can pre-emptively upgrade versions and/or plans prior to the event. Please read the details below for your specific plan type.

You can check which version of MongoDB your database is currently running by logging into the mLab management portal and looking at the lower-right corner of the connection information box on your deployment’s home page (sample screenshot of connection information box with MongoDB version).

Sandbox (version 3.0)

All of our free Sandbox databases running 3.0 will be upgraded to 3.2 during this scheduled window.

If you’d like to avoid this window, you can upgrade to any for-pay plan running 3.0 or 3.2 prior to this window (see pricing). Note that this will require a change to your connection string.

For-pay Shared (version 2.6)

All of our databases running 2.6 on shared virtual machines will be upgraded to 3.0 during this scheduled window.

If your database is upgraded to 3.0, applications that aren’t using MongoDB 3.0-compatible drivers may be unable to connect and authenticate.

If you’d like to avoid this scheduled maintenance window, you can self-service your upgrade to 3.0 prior to this window.

If you’d like to stay on 2.6, you can upgrade to a Dedicated plan running 2.6 prior to the window (see pricing). Please note, however, that we plan to discontinue support for 2.6 in the first half of 2017 on our Dedicated plans as well. Upgrades to Dedicated Cluster plans are seamless using our rolling node replacement process.

What deployments will not be impacted by this maintenance window?

Deployments running version 3.0 and above as well as Dedicated plan deployments will not be affected by this maintenance window.

For-pay Shared (version 3.0)

Your database will not be impacted by this maintenance window. That being said, if you are using us via one of our Platform-as-a-Service partners, please note the default version for all newly provisioned databases will become 3.2 at the time of this scheduled window.

Dedicated (version 2.6)

Your database(s) will not be impacted by this maintenance window. However, please note that in the first quarter of 2017 we intend to discontinue 2.6 support on our Dedicated plans as well. We recommend that you carefully review the upgrade requirements for 3.0 and the upgrade requirements for 3.2 as soon as possible and plan accordingly.

Dedicated (version 3.0)

Your database(s) will not be impacted by this maintenance window. However, you can upgrade versions to 3.2 at any time; please be sure to carefully review the upgrade requirements for 3.2 first.

Additional questions?

Please contact us anytime at support@mlab.com with any questions, issues, or feedback that you may have.