[SERVER-58277] add minimal gdb pretty printer for oplog entry Created: 06/Jul/21 Updated: 29/Oct/23 Resolved: 13/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Benety Goh |
| 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 2021-07-26 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When symbolizing stack traces on secondary or initial syncing nodes, stack traces containing functions that accept the OplogEntry class such as applyCommand_inlock() and applyOperation_inlock() currently print the oplog entry as "...". In these scenarios, it would be useful for triaging purposes to see what kind of oplog entry the node is stuck trying to apply. It would be nice for the symbolizer/hang analyzer to use a pretty printer that allows us to see some basic information on the oplog entry such as timestamp and operation/command type in the stack trace. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 09/Jul/21 ] |
|
Author: {'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}Message: |
| Comment by Benety Goh [ 06/Jul/21 ] |
|
This would have been useful in debugging |