Details
-
Doc Removal
-
Resolution: Won't Do
-
Trivial - P5
-
4.2.0
-
None
Description
Description
The section on large number of collections] states, "For each database, a single namespace file (i.e. <database>.ns) stores all meta-data for that database, and each index and collection has its own entry in the namespace file. MongoDB places limits on the size of namespace files."
However, removed mmapv1 options] states that the ability to change nssize was removed as it is a MMAPv1-specific configuration option.
Additionally, the 4.0 version of the docs say that WiredTiger is not subject to a limitation in the size of the namespace file]. I'm unsure as to why this section was removed for 4.2 as there is a considerable amount of information on the internet about MongoDb's limit on the number of collections from the days of MMAPv1 - most of that information does not specify that it does not apply to WiredTiger.
So, I'm assuming that there's no explicit limit (although I'm sure a practical limit exists). If that's the case, the section about large numbers of collections should be updated.