[SERVER-70802] Mongod data directory and FTDC files not uploaded as part of timeout Created: 24/Oct/22 Updated: 29/Oct/23 Resolved: 21/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alex Neben | Assignee: | Juan Gu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 14 | ||||||||||||
| Description |
|
It would appear that FTDC data isn't being collected from a timeout failure. A project was undertaken to retrieve FTDC data from a timeout failure, including work done in |
| Comments |
| Comment by Githook User [ 21/Dec/22 ] |
|
Author: {'name': 'Juan Gu', 'email': 'juan.gu@mongodb.com', 'username': 'juangugit'}Message: |
| Comment by Max Hirschhorn [ 17/Nov/22 ] |
|
Juan, Tausif, and I walked through how PM-1569 achieved the hang analyzer causing data files to be uploaded.
The fundamental issue is that resmoke archival running depends on the hang analyzer killing the processes. However, step (5) is known to take a long enough time where the evergreen agent abandons the work in the timeout: phase of the Evergreen project configuration after 15 minutes. My proposal for The longer term outlook I have for collecting diagnostics for hangs is that we rely more on post-processing to get the same information we can from the live process. This has very much been the motivation for me creating https://github.com/visemet/gdb-mongodb-server to supplant the mongodb-dump-locks gdb command. |