Skip to content

Rate this page
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Percona Server for MongoDB 8.3.4-1 (2026-07-28)

Installation Upgrade

Technical Preview

Percona Server for MongoDB 8.3.4-1 is available as a technical preview.

We recommend that early adopters use this feature for testing purposes only and not in production environments.

We are pleased to announce the new major version of Percona Server for MongoDB 8.3.4-1 – the drop-in replacement for MongoDB Community Edition. Percona Server for MongoDB supports MongoDB Community protocols and drivers and enhances it with the enterprise-grade features for free, enabling you to effectively meet the requirements of your organization in terms of high-availability, reliability and data security.

This release of Percona Server for MongoDB includes the improvements and bug fixes of MongoDB 8.3.4 Community Edition .

Upgrade considerations

To upgrade to MongoDB 8.3 from an 8.0 deployment, the deployment must have featureCompatibilityVersion set to 8.0.

To check the version:

db.adminCommand( { getParameter: 1, featureCompatibilityVersion: 1 } )

Release Highlights

Software Bill of Materials (SBOM)

Percona Server for MongoDB (PSMDB) now provides Software Bills of Materials (SBOMs) for every release. SBOMs improve software supply chain transparency by documenting the components and dependencies included in a build. They are generated automatically as part of the release pipeline in the industry standard CycloneDX format.

SBOMs are distributed through the following channels:

  • GitHub: The latest SBOM is placed in the root of the percona/percona-server-mongodb main branch.

  • Binaries/Tarballs: An SBOM file is included in doc/percona-server-mongodb/sbom.cdx.json

  • Packages: For .deb and .rpm packages, the SBOM file is installed in a standard documentation directory such as /usr/share/doc/percona-server-mongodb-server/sbom.cdx.json.

  • Docker: The SBOM is attached directly to the Docker image as metadata.

Join Percona Squad

Participate in monthly SWAG raffles, get early access to new product features, and join invite-only “ask me anything” sessions with database performance experts. Interested? Fill in the form at squad.percona.com/mongodb .

Upstream Improvements

MongoDB 8.3 introduces a lot of significant changes. We recommend testing it on staging environments before using it in production.

The key upstream improvements include:

Query planning and aggregation

The $scoreFusion aggregation stage is now generally available, and new expressions support hashing, Extended JSON conversion, binary subtypes, and ObjectId generation.

Monitoring and diagnostics

New FTDC, serverStatus, query memory, and slow in-progress query metrics provide better visibility into query execution, connection pools, replication lag, and resource consumption.

Workload management

New controls help limit resource consumption from unauthenticated connections, respond to storage engine cache pressure, and manage retries when cluster members are overloaded. Text search operations can also spill intermediate results to disk instead of consuming unrestricted memory.

Sharding

The removeShard command is deprecated in favor of commands that provide more control over shard draining and removal. DDL operations on sharded clusters must now run through mongos.

Indexes and time series collections

MongoDB 8.3 introduces 2dsphere index version 4 as the default and changes how geospatial indexes handle documents containing both GeoJSON and legacy coordinates. It also adds validation and naming restrictions for time series collections.

Security

SCRAM-SHA-1 authentication can no longer be enabled when FIPS mode is active. MongoDB 8.3.4 also includes a fix for CVE-2026-11933.

For the complete list of upstream changes, see Release Notes for MongoDB 8.3 and Compatibility Changes in MongoDB 8.3 .

Changelog

New features

  • PSMDB-2150: Percona Server for MongoDB (PSMDB) now provides Software Bills of Materials (SBOMs) for every release.

  • PSMDB-2003: We have implemented caching of LDAP userToDNMapping to reduce the number of round-trips to the LDAP server during authentication and authorization. Caching is controlled by security.ldap.userToDNMapping (exposed as --ldapUserToDNMapping at startup and ldapUserToDNMapping at runtime). For detailed information, see our documentation.

  • PSMDB-2038: Percona Server for MongoDB now exposes LDAP userToDN cache statistics through the serverStatus command. These metrics provide visibility into cache utilization and effectiveness, helping administrators troubleshoot LDAP authentication latency, validate cache behavior after configuration changes, and optimize cache sizing for their workloads. The new ldap.userToDNCache section reports runtime information such as cache usage, hits, misses, and invalidations, making LDAP authentication performance easier to monitor and tune.

Tools packaged with this release

Percona Server for MongoDB packages the following MongoDB tools:

MongoDB Shell (mongosh): 2.9.2 — upstream release notes