[DOCS-4654] Explicitly note when the mongod/s process should be restarted by modifying a configuration parameter and not only a command line option Created: 13/Jan/15 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Gianfranco Palumbo | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 1 year, 14 weeks, 1 day ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Story Points: | 1 | ||||
| Description |
|
There are several tutorials in which there is a step to restart the mongod/s process with or without a specific parameter. Many of these don't mention that this parameters can be enabled/disabled/changed by modifying the configuration file; not only the command line parameter. For example if the process was restarted without directoryperdb, smallfiles or a different user it could cause several issues. Links:
One possible way on how to show this: |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |