[SERVER-83984] WiredTiger verbosity level is suppressed Created: 07/Dec/23 Updated: 07/Feb/24 |
|
| Status: | In Progress |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.3.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Shin Yee Tan | Assignee: | Gavin Peters |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | storex-shortlist | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Sprint: | Execution Team 2024-01-08, Execution Team 2024-01-22, Execution Team 2024-02-05, Execution Team 2024-02-19 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
When we set wiredtiger verbosity levels likeĀ here, wiredtiger does work to generate verbose messages. These messages are returned inĀ this callback to the server and will be logged based on the mongo verbosity level. By default, mongo verbosity levels are 0 so we end up suppressing these messages. If wiredtiger verbosity levels are set, we should be able to correctly map that to mongo log levels and use that instead of overriding it with the mongo log level. This may have been introduced during |
| Comments |
| Comment by Louis Williams [ 08/Dec/23 ] |
|
It sounds like these logs are valuable for Storage Engines engineers. We should re-enable these log messages by default. We're already spending time generating the log messages, but due to this bug, we're not actually writing them to the MongoDB log. |