Related
- Translating OData Queries to MongoDB in Java With Jamolingo
- Cutting P99 Latency From ~3.2s To ~650ms in a Policy‑Driven Authorization API (Python + MongoDB)
- Isolation Level for MongoDB Multi-Document Transactions (Strong Consistency)
- Building a 3D WebXR Game with WASI Cycles: Integrating WasmEdge, Wasmtime, and Wasmer to Invoke MongoDB, Kafka, and Oracle
Trending
- DZone
- Data Engineering
- Databases
- MongoDB 3.0.4 Released
MongoDB 3.0.4 Released
Join the DZone community and get the full member experience.
Join For FreeMongoDB 3.0.4 is out and is ready for production deployment. This release contains only fixes since 3.0.3, and is a recommended upgrade for all 3.0 users.
Fixed in this release:
- SERVER-17923 Creating/dropping multiple background indexes on the same collection can cause fatal error on secondaries
- SERVER-18079 Large performance drop with documents > 16k on Windows
- SERVER-18190 Secondary reads block replication
- SERVER-18213 Lots of WriteConflict during multi-upsert with WiredTiger storage engine
- SERVER-18316 Database with WT engine fails to recover after system crash
- SERVER-18475 authSchemaUpgrade fails when the system.users contains non MONGODB-CR users
- SERVER-18629 WiredTiger journal system syncs wrong directory
- SERVER-18822 Sharded clusters with WiredTiger primaries may lose writes during chunk migration
3.0 Release Notes | Downloads | All Issues
As always, please let us know of any issues.
– The MongoDB Team
MongoDB
Opinions expressed by DZone contributors are their own.
Related
-
Translating OData Queries to MongoDB in Java With Jamolingo
-
Cutting P99 Latency From ~3.2s To ~650ms in a Policy‑Driven Authorization API (Python + MongoDB)
-
Isolation Level for MongoDB Multi-Document Transactions (Strong Consistency)
-
Building a 3D WebXR Game with WASI Cycles: Integrating WasmEdge, Wasmtime, and Wasmer to Invoke MongoDB, Kafka, and Oracle
Partner Resources
×