Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
3.0.0-rc6
-
None
-
Fully Compatible
-
ALL
-
-
0
Description
ISSUE SUMMARY
When using the WiredTiger storge engine, methods to collect the size of each database for the output of the show databases operation in the mongo shell are inefficent, particularly with larger numbers of databases, collections, and indexes.
USER IMPACT
The show databases operation in the mongo shell can take a long time to return the listing of databases.
WORKAROUNDS
None.
AFFECTED VERSIONS
MongoDB 3.0.0 through 3.0.4.
FIX VERSION
The fix is included in the 3.0.5 production release.
Original description
When running the show databases command, with only 20 databases, we're seeing extremely long response times, typically of 60-90 seconds.
Based on previous conversations, I'm curious if this might be related to checking database sizes and/or stating files.
> show databases
|
Admin 0.000GB
|
BTest 0.003GB
|
Config 0.000GB
|
Customer-Fox 0.012GB
|
Customer-CBS 0.040GB
|
Customer-NBC 0.004GB
|
Elmah 0.000GB
|
MBTest 0.004GB
|
Master 0.033GB
|
Monitoring 0.021GB
|
OCRM 0.009GB
|
OCarp 0.085GB
|
ODev 0.134GB
|
OP 0.041GB
|
Provisions 0.002GB
|
Queue 0.009GB
|
local 0.000GB
|
Attachments
Issue Links
- is depended on by
-
WT-1973 MongoDB changes for WiredTiger 2.7.0
-
- Closed
-
- is related to
-
SERVER-25025 Improve startup time when there are tens of thousands of collections/indexes on WiredTiger
-
- Closed
-
- related to
-
SERVER-16353 listDatabases is very slow on wiredtiger primary
-
- Closed
-
-
WT-1634 Opening a cursor with many tables is slow
-
- Closed
-