-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: 3.2.5
-
Component/s: Storage
-
Labels:None
-
Environment:Windows, all variants
-
Fully Compatible
-
ALL
-
Platforms 14 (05/13/16), Platforms 15 (06/03/16), Platforms 16 (06/24/16), Platforms 17 (07/15/16), Platforms 18 (08/05/16), Platforms 2016-08-26, Platforms 2016-09-19
Even after SERVER-23570 is fixed, Windows will exhibit a limit to the number of databases that can be created with on-disk encryption enabled. Today that limit is ~30, after the fix to SERVER-23570 it will be ~5000 (this is an estimate). But there is no reason for this to be a fixed limit at all, it could scale to whatever the environment is able to handle.
In Linux the same sort of limits will occur (in fact, the limits are lower by default), but they are adjustable at the operating system level using the instructions in DOCS-6885. There are no equivalent instructions for Windows.
Windows requires an API call; SetProcessWorkingSetSize and MongoDB could try this when it gets the error code indicating that locked limit has been reached.
- is depended on by
-
SERVER-22555 Use SecureString/SecureVector whenever appropriate
-
- Backlog
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-