Issue description
We have identified several critical issues which may affect your cluster(s). Review the following details for more information on each issue. You can also find summaries and additional links on our Alerts Page.
Write concern errors may be incorrectly suppressed when write commands fail or when the create command succeeds on a sharded cluster. This occurs only on sharded clusters OR on standalone replica sets using queryable encryption.
See SERVER-113256 for details and recommendations.
When
apiVersionis explicitly set, cross-shard transactions may silently be partially committed during failover events.See SERVER-106075 for details and recommendations.
On MongoDB 8.0 and later, cross-shard transactions may silently be partially committed if a cluster undergoes a point-in-time (PIT) restore. Lowering the
TransactionRecordMinimumLifetimeMinutessetting might also increase the likelihood of partial commits.See SERVER-105751 for details and recommendations.
On MongoDB 8.0 and later, 2dsphere indexes on metric data in time series collections are not correctly maintained when inserting data, which can result in incomplete geospatial query results.
See SERVER-112520 for details and recommendations, including repairing affected indexes.
For Atlas customers: Affected indexes have already been repaired or are in the process of being repaired.
Fixes and remediation
MongoDB patch versions 7.0.26, 8.0.16, and 8.2.2 contain fixes for all listed issues.
For MongoDB Atlas Customers: Your Atlas clusters have already been upgraded, unless you have configured a maintenance window. If you have a configured maintenance window, the change will apply during the next scheduled window or you may choose to apply the change immediately using the Begin Maintenance Now button.
If you have any questions, open a support case or start a chat with the Support team.