-
Type: Improvement
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: 3.2.6, 3.2.7, 3.2.8
-
Component/s: Performance, WiredTiger
-
None
-
Fully Compatible
-
v4.2, v4.0, v3.6
-
Execution Team 2019-09-23, Execution Team 2019-10-07
-
(copied to CRM)
-
15
mongod opens every collection and index upon startup to clear plan cache and ensure settings are correct for the current version. When there are tens or hundreds of thousands of collections and index (1 file per collection/index) this can take minutes to complete, even on very fast storage. Consider an option to do this in parallel to improve startup time.
Original Description
When starting the mongod service in a replicaset with ~50GB of data on extremely high-performance disk, it's taking approximately 2 minutes before the mongo database becomes available. This seems like a large regression from the 2.8 and 3.0 days.
- is duplicated by
-
SERVER-31155 High memory & resources usage + very long boot time with many DBs
- Closed
-
SERVER-40130 Improve multi-threading
- Closed
- is related to
-
SERVER-52833 Capped collections can contain too many documents after replication recovery
- Closed
-
SERVER-43664 Speedup WiredTiger storage engine startup for many tables by optimizing WiredTigerUtil::setTableLogging()
- Closed
- related to
-
SERVER-17078 show databases taking extraordinarily long with wiredTiger
- Closed
-
SERVER-17675 Support file per database for WiredTiger
- Closed