[SERVER-34568] Ability to enable authentication without stoping mongod for stand alone using the InMemory storage engine. Created: 19/Apr/18 Updated: 27/Oct/23 Resolved: 30/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Security |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Jorge Imperial-Sosa | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
While we have a way for enabling authentication on Replica Sets and Sharded Clusters without any down time in MongoDB 3.4+, we do not have that option currently for Standalone hosts. This is particularly important in the case of hosts running with the InMemory Storage Engine, because they have to reload all the information in the database, incurring in a much larger downtime than other storage engines. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 30/Apr/18 ] |
|
Standalone deployments are not highly available by design. Use replica sets for highly available deployments. |