-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
JDK-8284165: Add pid to process reaper thread name #8070
JDK-8284165: Add pid to process reaper thread name #8070
Conversation
👋 Welcome back stuefe! A progress list of the required criteria for merging this PR into |
GHA: windows x64 error unrelated |
Webrevs
|
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.
LGTM
A refactoring of the run method would be ok, but not essential.
@tstuefe This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 18 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
Thanks @AlanBateman and @RogerRiggs ! /integrate |
Going to push as commit 9561b5e.
Your commit was automatically rebased without conflicts. |
To help with analyzing fork-heavy scenarios, it would help if we could see at one glance which process a reaper is servicing. A pragmatic way would be to add the pid to its name - that way, e.g. thread dumps with lots of reaper threads would be more enlightening.
Since reaper threads get reused we have to change the name back to some base name when the reaper is done with the process. This has the additional benefit of showing us in the thread dump which reapers are actually reaping, and which are just idling around in the pool.
With this patch, reaper threads are:
Tests:
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8070/head:pull/8070
$ git checkout pull/8070
Update a local copy of the PR:
$ git checkout pull/8070
$ git pull https://git.openjdk.java.net/jdk pull/8070/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8070
View PR using the GUI difftool:
$ git pr show -t 8070
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8070.diff