MongoDB 6.0.17 is out and is ready for production deployment. This release contains only fixes since 6.0.16, and is a recommended upgrade for all 6.0 users.
Fixed in this release:
- SERVER-85892 $merge with pipeline after $documents returns error
- SERVER-91195 Provide a generic backportable solution not to miss top-level timeseries collection options
- SERVER-91362 Performance: Do not copy JS "scope" object if a cached JsExecution exists
- SERVER-91406 $changeStreamSplitLargeEvent returns Location7182803 error when used with non-renameable match expression
- WT-12708 Evaluation/Revision of eviction random traversal
6.0 Release Notes |
All Issues |
All Downloads
As always, please let us know of any issues.
-- The MongoDB Team
1 Like
Hi,
This week until yesterday (August 27/2024), I was able to create a few v6 clusters in Atlas; they all were created using v6.0.17
Today (August 28/2024), I created a new v6 cluster, but Atlas used v6.0.16
Any idea why this happened? This prevents me from migrating some clusters (running on v6.0.17) to new Atlas projects.
I appreciate any help you can provide.
Quick update:
I tried again after a couple of hours, and Atlas is creating the v6 clusters using version 6.0.17
It looks like the issue was fixed.
Vlad
system
(system)
Closed
4
This topic was automatically closed after 90 days. New replies are no longer allowed.