Recently, one of our customers reported a problem after upgrading a sharded cluster from MongoDB 5.0 to 6.0. The upgrade of data-bearing nodes was fine, but in the final part of the process, where mongos routers needed to be restarted, the new version did not go well. This caused problems for the applications, where suddenly ..read more

Managing database users within complex CICD pipelines and GitOps workflows has long been a challenge for MongoDB deployments. With Percona Operator for MongoDB 1.17, we introduce a new feature, currently in technical preview, that streamlines this process. Now, you can create the database users you need directly within the operator, eliminating the need to wait ..read more

MongoDB high availability is essential to ensure reliability, customer satisfaction, and business resilience in an increasingly interconnected and always-on digital environment. Ensuring high availability for database systems introduces complexity, as databases are stateful applications. Adding a new operational node to a cluster can take hours or even days, depending on the dataset size. This is ..read more

I have always been wondering about performance regression when upgrading in MongoDB. From MongoDB v3.6, despite continuous improvement in the MongoDB feature development, the growing feature set has not included much, if anything in the way of performance improvements. At Percona, we always strive to boost the overall performance by looking into the customers’ environment ..read more

This article is, in fact, two topics merged into one publication. Both are related to anonymous statistical data collection within Percona releases of database engines: MySQL, MongoDB, and PostgreSQL. In the first part of this article, I will share some of our findings and observations and discuss the various conclusions we have drawn from them ..read more

When working with MongoDB replication in environments using the WiredTiger storage engine, you may encounter data size discrepancies between PRIMARY and SECONDARY nodes. When this problem arises, the SECONDARY node uses significantly more disk space than the PRIMARY instance. When this issue first appeared at Percona Support a few years ago, the most notable discussion ..read more

Data-at-rest encryption (also known as transparent data encryption or TDE) is a necessary mechanism for ensuring the security of a DBMS deployment. Upcoming releases of Percona Server for MongoDB extend that mechanism with the KMIP key state polling feature. In this technical post, I will describe how the feature works and how it helps reduce ..read more

Companies use specific database versions because they’re proven performers or because it’s hard to keep up with frequent releases. But lagging behind has some major issues. When it’s time to upgrade, is it better to update binaries through each major revision or skip versions? TL;DR: Upgrading a MongoDB cluster using backups and skipping versions is ..read more

In the previously posted blog, Compaction in Percona Server for MongoDB (PSMDB), we discussed how compact works before version 4.4. In this blog, we will see how compact works on PSMDB 6.0. I recommend reading the blog post linked above to understand what compact does, how to check dataSize, and how much space we can ..read more

Percona Everest is the first open source platform designed for automated database provisioning and management. It supports multiple database technologies and can be hosted on any Kubernetes infrastructure, in the cloud or on-premises. It provides an easy-to-use web interface while leveraging the power of the Percona Operators behind the scenes to do all the heavy ..read more