[SERVER-65158] Log some WiredTiger components at higher debug levels Created: 01/Apr/22 Updated: 29/Oct/23 Resolved: 20/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Louis Williams | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Execution Team 2022-05-16, Execution Team 2022-05-30 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 140 | ||||||||||||
| Description |
|
By "higher debug level" I mean at a level requiring a higher level of logging verbosity. All WiredTiger components with WT_VERBOSE_DEBUG messages log when the MongoD log component verbosity is 1 (i.e. "mongod -v"). This is too noisy. See Log the WT_VERBOSE_DEBUG messages for these components when the MongoDB log component verbosity is Info (or -1) to be consistent with 4.4:
Log the WT_VERBOSE_DEBUG messages for the remaining components when the MongoDB log component verbosity is at least 2. |
| Comments |
| Comment by Githook User [ 20/May/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 20/May/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: Revert " This reverts commit a3123bb71beb721fc0fa8beb6c35a7d9beb8a0ba. |
| Comment by Githook User [ 06/May/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |