- Reference >
- MongoDB Limits and Thresholds
MongoDB Limits and Thresholds¶
This document provides a collection of hard and soft limitations of the MongoDB system.
- BSON Document Size¶
The maximum BSON document size is 16 megabytes.
The maximum document size helps ensure that a single document cannot use excessive amount of RAM or, during transmission, excessive amount of bandwidth. To store documents larger than the maximum size, MongoDB provides the GridFS API. See mongofiles and the documentation for your driver for more information about GridFS.
- Namespace Length¶
Each namespace, including database and collection name, must be shorter than 123 bytes.
- Number of Namespaces¶
The limitation on the number of namespaces is the size of the namespace file divided by 628.
A 16 megabyte namespace file can support approximately 24,000 namespaces. Each collection and index is a namespace.
- Index Key Limit¶
The total size of an index entry, which can include structural overhead depending on the BSON type, must be less than 1024 bytes.
Changed in version 2.6: MongoDB 2.6 implements a stronger enforcement of the limit on index key:
MongoDB will not create an index on a collection if the index entry for an existing document exceeds the index key limit. Previous versions of MongoDB would create the index but not index such documents.
Reindexing operations will error if the index entry for an indexed field exceeds the index key limit. Reindexing operations occur as part of compact and repairDatabase commands as well as the db.collection.reIndex() method.
Because these operations drop all the indexes from a collection and then recreate them sequentially, the error from the index key limit prevents these operations from rebuilding any remaining indexes for the collection and, in the case of the repairDatabase command, from continuing with the remainder of the process.
MongoDB will not insert into an indexed collection any document with an indexed field whose corresponding index entry would exceed the index key limit, and instead, will return an error. Previous versions of MongoDB would insert but not index such documents.
Updates to the indexed field will error if the updated value causes the index entry to exceed the index key limit.
If an existing document contains an indexed field whose index entry exceeds the limit, any update that results in the relocation of that document on disk will error.
In MongoDB 2.6, secondary members of replica sets will continue to replicate documents with an indexed field whose corresponding index entry exceeds the index key limit on initial sync but will print warnings in the logs.
Secondary members also allow index build and rebuild operations on a collection that contains an indexed field whose corresponding index entry exceeds the index key limit but with warnings in the logs.
With mixed version replica sets where the secondaries are version 2.6 and the primary is version 2.4, secondaries will replicate documents inserted or updated on the 2.4 primary, but will print error messages in the log if the documents contain an indexed field whose corresponding index entry exceeds the index key limit.
For existing sharded collections, chunk migration will fail if the chunk has a document that contains an indexed field whose index entry exceeds the index key limit.
- Number of Indexes per Collection¶
A single collection can have no more than 64 indexes.
- Index Name Length¶
Fully qualified index names, which includes the namespace and the dot separators (i.e. <database name>.<collection name>.$<index name>), cannot be longer than 128 characters.
By default, <index name> is the concatenation of the field names and index type. You can explicitly specify the <index name> to the ensureIndex() method to ensure that the fully qualified index name does not exceed the limit.
- Number of Indexed Fields in a Compound Index¶
There can be no more than 31 fields in a compound index.
- Queries cannot use both text and Geospatial Indexes¶
You cannot combine the text command, which requires a special text index, with a query operator that requires a different type of special index. For example you cannot combine text command with the $near operator.
- Fields with 2dsphere Indexes can only hold Geometries¶
Fields with 2dsphere indexes must hold geometry data in the form of coordinate pairs or GeoJSON data. If you attempt to insert a document with non-geometry data in a 2dsphere indexed field, or build a 2dsphere index on a collection where the indexed field has non-geometry data, the operation will fail.
The unique indexes limit in Sharding Operational Restrictions.
- Maximum Number of Documents in a Capped Collection¶
Changed in version 2.4.
If you specify a maximum number of documents for a capped collection using the max parameter to create, the limit must be less than 232 documents. If you do not specify a maximum number of documents when creating a capped collection, there is no limit on the number of documents.
- Data Size¶
A single mongod instance cannot manage a data set that exceeds maximum virtual memory address space provided by the underlying operating system.
Virtual Memory Limitations Operating System Journaled Not Journaled Linux 64 terabytes 128 terabytes Windows Server 2012 R2 and Windows 8.1 64 terabytes 128 terabytes Windows (otherwise) 4 terabytes 8 terabytes
- Number of Collections in a Database¶
The maximum number of collections in a database is a function of the size of the namespace file and the number of indexes of collections in the database.
See Number of Namespaces for more information.
- Number of Members of a Replica Set¶
Replica sets can have no more than 12 members.
- Number of Voting Members of a Replica Set¶
Replica sets can have up to 7 voting members. For replica sets with more than 7 total members, see Non-Voting Members.
- Sorted Documents¶
MongoDB will only return sorted results on fields without an index if the combined size of all documents in the sort operation, plus a small overhead, is less than 32 megabytes.
- Aggregation Pipeline Operation¶
Changed in version 2.6.
Pipeline stages have a limit of 100 megabytes of RAM. If a stage exceeds this limit, MongoDB will produce an error. To allow for the handling of large datasets, use the allowDiskUse option to enable aggregation pipeline stages to write data to temporary files.
- 2d Geospatial queries cannot use the $or operator¶
- Area of GeoJSON Polygons¶
For $geoIntersects or $geoWithin queries, GeoJSON geometries must have an area less than the area of a single hemisphere. For geometries larger than a single hemisphere, MongoDB queries for the smaller of the complementary geometries. For geometries equal to a single hemisphere, MongoDB makes no guarantees as to which geometry (the specified geometry or the complementary) it uses.
- Database Name Case Sensitivity¶
MongoDB does not permit database names that differ only by the case of the characters.
- Restrictions on Database Names for Windows¶
Changed in version 2.2: Restrictions on Database Names for Windows.
For MongoDB deployments running on Windows, MongoDB will not permit database names that include any of the following characters:
Also, database names cannot contain the null character.
- Restrictions on Database Names for Unix and Linux Systems¶
For MongoDB deployments running on Unix and Linux systems, MongoDB will not permit database names that include any of the following characters:
Also, database names cannot contain the null character.
- Length of Database Names¶
Database names cannot be empty and must have fewer than 64 characters.
- Restriction on Collection Names¶
New in version 2.2.
Collection names should begin with an underscore or a letter character, and cannot:
- contain the $.
- be an empty string (e.g. "").
- contain the null character.
- begin with the system. prefix. (Reserved for internal use.)