[SERVER-50502] The lock manager dump logv2 message needs logv2::LogTruncation::Disabled set so that lock dumps are not truncated Created: 24/Aug/20 Updated: 29/Oct/23 Resolved: 27/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Execution Team 2020-09-07 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 14 | ||||||||
| Description |
|
Investigating a test failure I noticed that the lock manager dump had a "truncated" message at the end,
Logv2 messages need logv2::LogTruncation::Disabled set in order to avoid truncation. The lock manager dump logv2 message does not currently have this set. It would also be great if we could get the log message to span multiple lines instead of being scrunched into a single really long line that's hard to read, but I don't know how to do that. |
| Comments |
| Comment by Githook User [ 20/Nov/20 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: (cherry picked from commit c77fd1a19153af5cbf22355167298b0644c7c7cd) |
| Comment by Githook User [ 27/Aug/20 ] |
|
Author: {'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}Message: |