Skip to content

Commit c44fbb5

Browse files
author
Dave Cuthbert
authored
DOCS-13797 BACKPORT (#1748)
1 parent ff00953 commit c44fbb5

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed

source/reference/parameters.txt

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1095,6 +1095,39 @@ General Parameters
10951095

10961096
mongod --setParameter failIndexKeyTooLong=false
10971097

1098+
1099+
.. parameter:: maxNumActiveUserIndexBuilds
1100+
1101+
|mongod-only|
1102+
1103+
*Type*: integer
1104+
1105+
*Default*: 3
1106+
1107+
MongoDB limits the number of concurrent user index builds to control
1108+
WiredTiger cache pressure. The primary node can run up to
1109+
``maxNumActiveUserIndexBuilds`` concurrent user index builds. This is
1110+
a global limit that applies across collections.
1111+
1112+
System indexes are not limited to ``maxNumActiveUserIndexBuilds``,
1113+
however a running system index build will count against the limit for
1114+
user index builds.
1115+
1116+
After reaching ``maxNumActiveUserIndexBuilds``, MongodDB blocks
1117+
additional user index builds until the number of concurrent index
1118+
builds drops below the ``maxNumActiveUserIndexBuilds`` limit. If an
1119+
index build is blocked, the server logs a message, "Too many index
1120+
builds running simultaneously, waiting until the number of active
1121+
index builds is below the threshold".
1122+
1123+
The following command sets a limit of 4 concurrent index builds:
1124+
1125+
.. code-block:: javascript
1126+
1127+
db.adminCommand( { setParameter: 1, maxNumActiveUserIndexBuilds: 4 } )
1128+
1129+
See also: :parameter:`maxIndexBuildMemoryUsageMegabytes`
1130+
10981131
.. parameter:: notablescan
10991132

11001133
|mongod-only|

0 commit comments

Comments
 (0)