[SERVER-29031] Allow SecureAllocator to be enabled or disabled at startup Created: 01/May/17 Updated: 27/Oct/23 Resolved: 30/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Jackson | Assignee: | Shreyas Kalyan |
| Resolution: | Gone away | Votes: | 2 |
| Labels: | platforms-re-triaged | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Sprint: | Security 2019-08-12 |
| Participants: |
| Description |
|
Many Linux systems limit the amount of memory which may be mlocked to low values. As we use more locked memory, users may hit this limit. We should allow the allocator which provides access to this resource to be enabled or disabled. On community it should be disabled by default, as these users have not previously experienced a need to configure ulimits. |
| Comments |
| Comment by Shreyas Kalyan [ 30/Jul/19 ] |
|
Looks like this was done inĀ https://jira.mongodb.org/browse/SERVER-30821. The correct method of disabling SecureAllocator for all domains in the server is to run it with --setParameter disabledSecureAllocatorDomains=* and the correct method of disabling SecureAllocator for all domains in the shell is to run it with --setShellParameter disabledSecureAllocatorDomains=*. Closing as Gone away. |
| Comment by Justin Cohler [ 05/May/17 ] |
|
We'd like to backport the memory impacting work in 3.4 before moving on with this ticket. |