-
Notifications
You must be signed in to change notification settings - Fork 63
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
agent: use a timeout when shutting down the runtime #1334
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no action: it would be really nice to get a trace of what tasks still haven't stopped after this timeout. Was that feasible in your investigations?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, what I found was the dump function, which can give you a nice stack trace for each running task. But it comes with quite a few caveats, which made me pretty hesitant to start using it without further investigation and testing.
Probably the biggest caveat is that it can't actually produce a dump if any tasks are synchronously deadlocked. I'm unsure of what this means for i/o tasks that are using blocking threads. But dumps are also linux-only, and require enabling "unstable" features of tokio (I'm not 100% clear on the implications of that).
IMO it's potentially still worth investigating, though it might be better to wait for more progress on the stabilization. They have a stabilization issue in the tokio repo with a sizeable TODO list.
That said, if all we want is just a list of still-running tasks, the
tokio-console
does at least provide that. The console still requires enabling "unstable" features, but otherwise seems to have fewer caveats, but also can't provide stack traces. I'd opted not to add it, mostly due to apprehension over enabling the unstable features. But could look into the unstable feature more, if you reckon it's worth the time (I was just trying to time-box my investigation to an hour)