Video Transcript (English)

Congratulations on completing this unit on self-managed upgrades and maintenance in MongoDB!

Upgrading and maintaining your MongoDB database is a crucial task for a database administrator. MongoDB has features that enable us to do these tasks in a rolling fashion, which means that our database experiences zero downtime.

Let’s quickly recap what we covered in this unit.

First, you learned that MongoDB minimizes downtime by leveraging replica sets to perform rolling maintenance.

We also identified some scenarios that require maintenance, such as: Upgrading to a new version of MongoDB, upgrading MongoDB client drivers, security updates to the operating system, changes to replica set membership, and upgrading operating systems.

Next, you learned how to read the compatibility tables in the MongoDB driver documentation, which is an essential step to take before upgrading.

Then, we explored how upgrading can affect the performance of your application in different ways.

You also learned that the Stable API allows you to upgrade your MongoDB server at will, and ensure that behavior changes between MongoDB versions won’t break your application.

Next, we went over the checklist of tasks to do before upgrading MongoDB versions.

You learned how to find the oplog window, which is the time difference between the newest and the oldest timestamps in the oplog. The oplog window gives us a rough estimate of how much time we have to perform maintenance on a single node.

Then we went through all of the steps involved in upgrading the MongoDB version on Ubuntu Linux.

Now that you know the basics of upgrading and maintaining a MongoDB database, you might want to check out the units on server administration and Atlas upgrades and maintenance.

You can also visit MongoDB’s documentation.

Until next time, keep learning!