Alex Cercel (Rackspace) delivers the talk, "Upgrading to MongoDB 4.0 From Older Versions", on DAY 1 of the Percona Live Open Source Database Conference 2019, 5/29, at Austin, TX.
The changes that MongoDB is bringing to the world in 4.0 are tempting to many companies and administrators, but if you are on an older version such as 3.2, upgrading with minimum disruption can be challenging.
Some of the problems that a company might face are that older language drivers versions may not be compatible with newer versions of mongo, the upgrade path might change, and there is a lot of documentation to read before you embark on the upgrade path.
If in 3.2 the config servers could be both mirrored or replica sets, in 3.4, it's a must to have the config servers as replica sets. Upgrading without interruption can be difficult. With so many things to read about, it's always good to have a reference that will give you an understanding of things that you should consider. A form of cheat sheet.
In this 50 minutes session, I would like to present the steps needed to move from 3.2 to 3.4, which will include some tips to upgrade the config servers to replica sets with minimal disruption and from 3.4 to 3.6 and from 3.6 to 4.0, again, with minimal disruption.
The session will also mention best practices that will apply when running any version upgrade.
MongoDB Atlas vs Managed Community Edition
Converting MongoDB to Percona Server for MongoDB
Moving MongoDB to the Cloud: Strategies and Points To Consider
Using MongoDB with Kafka - Use Cases and Best Practices - Antonio Giannopoulos - Percona Live ONLINE
In and out of the weeds with MongoDB 4.4 Hedged Reads - PLO October 2020
The State of MongoDB, Its Open Source Community, and Where Percona Is Going With It