Skip to content

Commit b30745c

Browse files
author
Dave Cuthbert
authored
DOCS-13797 BACKPORT (#1749)
1 parent 9ec8217 commit b30745c

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
@@ -1047,6 +1047,39 @@ General Parameters
10471047

10481048
mongod --setParameter failIndexKeyTooLong=false
10491049

1050+
1051+
.. parameter:: maxNumActiveUserIndexBuilds
1052+
1053+
|mongod-only|
1054+
1055+
*Type*: integer
1056+
1057+
*Default*: 3
1058+
1059+
MongoDB limits the number of concurrent user index builds to control
1060+
WiredTiger cache pressure. The primary node can run up to
1061+
``maxNumActiveUserIndexBuilds`` concurrent user index builds. This is
1062+
a global limit that applies across collections.
1063+
1064+
System indexes are not limited to ``maxNumActiveUserIndexBuilds``,
1065+
however a running system index build will count against the limit for
1066+
user index builds.
1067+
1068+
After reaching ``maxNumActiveUserIndexBuilds``, MongodDB blocks
1069+
additional user index builds until the number of concurrent index
1070+
builds drops below the ``maxNumActiveUserIndexBuilds`` limit. If an
1071+
index build is blocked, the server logs a message, "Too many index
1072+
builds running simultaneously, waiting until the number of active
1073+
index builds is below the threshold".
1074+
1075+
The following command sets a limit of 4 concurrent index builds:
1076+
1077+
.. code-block:: javascript
1078+
1079+
db.adminCommand( { setParameter: 1, maxNumActiveUserIndexBuilds: 4 } )
1080+
1081+
See also: :parameter:`maxIndexBuildMemoryUsageMegabytes`
1082+
10501083
.. parameter:: notablescan
10511084

10521085
|mongod-only|

0 commit comments

Comments
 (0)