[SERVER-41352] Incorrect verbose configuration in the wiredtiger connection string Created: 29/May/19 Updated: 29/Oct/23 Resolved: 18/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.0-rc2, 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sulabh Mahajan | Assignee: | Zach Yam (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Backport Requested: |
v4.2
|
||||||||||||
| Sprint: | Execution Team 2019-06-17, Execution Team 2019-07-01 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
While debugging another ticket I noticed the following WT connection string is being used by MongoDB:
This comes from the following string generation code in WiredTigerKVEngine::WiredTigerKVEngine():
If a configuration option is repeated, verbose=(recovery_progress),verbose=(checkpoint_progress), the last option overwrites the prior options. So, in this case, we would never put verbose output for recovery-progress. If the above if-condition is true "verbose=(recovery)" will overwrite other verbose types. It is best to construct a verbose option string of the following form:
It is worthwhile evaluating if there are other WT options that might be getting overwritten and ignored like the above case. |
| Comments |
| Comment by Githook User [ 21/Jun/19 ] |
|
Author: {'name': 'Zach Yam', 'username': 'zachyam', 'email': 'zach.yam@mongodb.com'}Message: (cherry picked from commit 99e7f57e7e5eb63f22e2b582a10e78c197b835e6) |
| Comment by Githook User [ 18/Jun/19 ] |
|
Author: {'name': 'Zach Yam', 'email': 'zach.yam@mongodb.com', 'username': 'zachyam'}Message: |