[SERVER-39374] diagnostic.data directory prepends name of mongos log to generate the directory name Created: 05/Feb/19 Updated: 27/Oct/23 Resolved: 08/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | 3.4.19, 3.6.10, 4.0.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Enrique Garnelo Prediger | Assignee: | Bruce Lucas (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Tested in 3.4.19, 3.6.10 and 4.0.5 finding consistent results in all these versions. For example if the logpath for the mongos process is set to /data/mongos/enrique.log the diagnostic.data directory will be named enrique.diagnostic.data. Expected behaviour |
| Comments |
| Comment by Bruce Lucas (Inactive) [ 05/Feb/19 ] |
|
For mongos there is no dbPath, so the diagnostic.data directory can't be located in the same place as for mongod, and this is the reason for basing the default location on the mongos log file. However for mongos (only) there is a diagnosticDataCollectionDirectoryPath parameter that allows you to specify a location for the diagnostic.data directory. Details are documented here. Does this meet your requirements? |