[SERVER-30394] ftdc file_manager generates an incorrect absolute diagnostic data path for mongos if the logpath is a relative path Created: 28/Jul/17 Updated: 30/Oct/23 Resolved: 07/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.11 |
| Fix Version/s: | 3.5.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James O'Leary | Assignee: | Mark Benvenuto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Steps To Reproduce: | Configure a mongos with the following conf file excerpt or commmand line parameter '--logpath 12345/mongos.log' and the mongos from say '/tmp/mongos.ftdc':
Check '/tmp/mongos.ftdc/12345/mongos.log':
Conf file:
|
||||||||||||
| Sprint: | Platforms 2017-08-21 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Both --logpath and systemLog.path can accept relative paths and correctly converts them based on the CWD. However, when a relative path is passed to FTDCFileManager::create, it is incorrectly converted to an absolute path off the root file system. While using relative paths for configuration parameters is probably not the expected use case, the ftdc code should work in the same fashion as logging. |
| Comments |
| Comment by Githook User [ 07/Aug/17 ] |
|
Author: {'username': 'markbenvenuto', 'email': 'mark.benvenuto@mongodb.com', 'name': 'Mark Benvenuto'}Message: |