[SERVER-58947] servers.js passes logComponentVerbosity only to latest mongod binary Created: 29/Jul/21 Updated: 29/Oct/23 Resolved: 25/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Vishnu Kaushik | Assignee: | Vishnu Kaushik |
| 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 | ||||||||
| Sprint: | Repl 2021-10-18, Repl 2021-11-01 | ||||||||
| Participants: | |||||||||
| Description |
|
The logComponentVerbosity (and other parameters) are being passed only to the latest mongod binary, as seen here. Because of this, when we are running multiversion tests, older binaries such as the mongod-5.0 do not have their logComponentVerbosities set. |
| Comments |
| Comment by Githook User [ 25/Oct/21 ] |
|
Author: {'name': 'Vishnu Kaushik', 'email': 'vishnu.kaushik@mongodb.com', 'username': 'kauboy26'}Message: |
| Comment by Robert Guo (Inactive) [ 13/Sep/21 ] |
|
There's a general problem of not knowing which options correspond to which version for shell fixtures since they are all invoked through the same shell. But people in general prefer a more flexible, less centralized configuration format at the expense of some code hygiene and readability. So we're holding our breath on infrastructure changes here. I think a possible solution for this particular Server option is to add an else-if statement for when the binary name is "mongod-$lastContinuous" (e.g. mongod-5.0) and duplicate the logging options there. Reassigning to Repl to evaluate and/or implement this addition. |