Skip to content

Commit fca2a11

Browse files
author
Sam Kleinman
committed
DOCS-4684: changes in limits for wt
1 parent c978d60 commit fca2a11

File tree

1 file changed

+30
-15
lines changed

1 file changed

+30
-15
lines changed

source/reference/limits.txt

Lines changed: 30 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -32,24 +32,31 @@ Namespaces
3232
Each namespace, including database and collection name, must be
3333
shorter than 123 bytes.
3434

35-
.. fix when we know what the actual limit is.
36-
3735
.. _limit-number-of-namespaces:
3836
.. limit:: Number of Namespaces
3937

40-
The limitation on the number of namespaces is the size of the
41-
namespace file divided by 628.
38+
.. versionchanged:: 3.0
39+
40+
For the MMAPv1 the number of namespaces is limited to the size of
41+
the namespace file divided by 628.
4242

4343
A 16 megabyte namespace file can support approximately 24,000
4444
namespaces. Each collection and index is a namespace.
4545

46+
The WiredTiger storage engine is *not* subject to this limitation.
47+
4648
.. _limit-size-of-namespace-file:
4749
.. limit:: Size of Namespace File
4850

49-
Namespace files can be no larger than 2047 megabytes.
51+
.. versionchanged:: 3.0
52+
53+
For the MMAPv1 storage engine, namespace files can be no larger
54+
than 2047 megabytes.
5055

5156
By default namespace files are 16 megabytes. You can configure the
52-
size using the :setting:`~storage.nsSize` option.
57+
size using the :setting:`~storage.mmapv1.nsSize` option.
58+
59+
The WiredTiger storage engine is *not* subject to this limitation.
5360

5461
.. _index-limitations:
5562

@@ -128,9 +135,11 @@ Data
128135
.. _limit-data-size:
129136
.. limit:: Data Size
130137

131-
A single :program:`mongod` instance cannot manage a data set that
132-
exceeds maximum virtual memory address space provided by the
133-
underlying operating system.
138+
.. versionchanged:: 3.0
139+
140+
Using the MMAPv1 storage engine, a single :program:`mongod`
141+
instance cannot manage a data set that exceeds maximum virtual
142+
memory address space provided by the underlying operating system.
134143

135144
.. list-table:: Virtual Memory Limitations
136145
:widths: 15 10 10
@@ -149,11 +158,17 @@ Data
149158
- 4 terabytes
150159
- 8 terabytes
151160

161+
The WiredTiger storage engine is *not* subject to this limitation.
162+
152163
.. limit:: Number of Collections in a Database
153164

154-
The maximum number of collections in a database is a function of
155-
the size of the namespace file and the number of indexes of
156-
collections in the database.
165+
.. versionchanged:: 3.0
166+
167+
For the MMAPv1 storage engine, the maximum number of collections in
168+
a database is a function of the size of the namespace file and the
169+
number of indexes of collections in the database.
170+
171+
The WiredTiger storage engine is *not* subject to this limitation.
157172

158173
See :limit:`Number of Namespaces` for more information.
159174

@@ -164,9 +179,9 @@ Replica Sets
164179

165180
.. versionchanged:: 3.0.0
166181

167-
Replica sets can have up to 50 members; however, not all drivers are
168-
suitable for use with large replica sets. For more information, see
169-
:ref:`3.0-replica-sets-max-members`.
182+
Replica sets can have up to 50 members. See
183+
:ref:`3.0-replica-sets-max-members` for more information about
184+
specific driver compatibility with large replica sets.
170185

171186
.. limit:: Number of Voting Members of a Replica Set
172187

0 commit comments

Comments
 (0)