[SERVER-3181] Add option to listDatabases to only get db names, not size info Created: 02/Jun/11 Updated: 15/Nov/21 Resolved: 20/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.13, 3.4.3, 3.5.4 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Lei Zhang | Assignee: | Geert Bosch |
| Resolution: | Done | Votes: | 10 |
| Labels: | PM248, bkp, commands, listDatabases, performance | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Linux yq131 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux |
||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v3.4, v3.2
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Storage 2017-03-06 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
I have about 29377 files (including datafile and nsfile), 13666 databases. The total size is about 1TB. The mongod started with parameters "smallfiles" and "noprealloc". |
| Comments |
| Comment by Githook User [ 19/Mar/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit fff6d490ce43a6d3952cf2352f81c524b20e6f49) Substantial changes were necessary for the backport, as the listDatabases command does not Conflicts: |
| Comment by Githook User [ 03/Mar/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: (cherry picked from commit fff6d490ce43a6d3952cf2352f81c524b20e6f49) |
| Comment by Eric Milkie [ 28/Feb/17 ] |
|
It is currently scheduled to be backported to the 3.2 branch. |
| Comment by Chad Kreimendahl [ 28/Feb/17 ] |
|
Will this be backported to 3.2, as requested? |
| Comment by Githook User [ 20/Feb/17 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |
| Comment by Chad Kreimendahl [ 19/Jan/17 ] |
|
I'm thinking this happens on more than "initial sync", as we're seeing it happen 1x per replica member per minute. |
| Comment by Zhang Youdong [ 13/Jul/16 ] |
|
continue the discuss on SERVER-24948 I create a pull request, see https://github.com/mongodb/mongo/pull/1100, and I will use it in our production environment. Scott Hernandez I have rethink this change based on your tips.
In summary, my opinion is:
|
| Comment by Scott Hernandez (Inactive) [ 08/Jul/16 ] |
|
Taking a look at this for initial sync improvements for 3.4 |