-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cli: take multiple pprof snapshots from 'operator debug' #11514
Comments
@tgross is this something a new contributor should pick up? |
It's probably fairly straightforward to pick up. I think there's a bit of UX interaction to figure out here as we have an Also, just a heads up we have a few other |
Haven't yet finalized on the flag, will wait for @davemay99's suggestion for that but I went ahead and did a simple implementation using a new
I haven't raised a PR yet but If you think this change here looks like its in the right direction, I'll raise a PR. |
subtle reminder, feel free to ignore otherwise. @tgross |
Hi @danishprakash that seems more-or-less the right idea. Can you open it as a PR? That'd help me loop in @davemay99 as well. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
A long-running
nomad operator debug
command gets logs and raft snapshots over a window of time, but only takes pprof profiles (for heap, goroutines, cpu profiling, etc.) at the start of the run. Most of the time this is enough, but being able to take several snapshots of profiles could be useful for debugging the internals over a period of time.Example use cases:
chan receive
orselect
states change their states or whether they continue to block. This can help Nomad engineers figure out whether a goroutine is blocked from a deadlock (bug) or just experiencing backpressure.The text was updated successfully, but these errors were encountered: