8196743: jstatd doesn't see new Java processes inside Docker container#3908
8196743: jstatd doesn't see new Java processes inside Docker container#3908kevinjwalls wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back kevinw! A progress list of the required criteria for merging this PR into |
|
@kevinjwalls The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
...ternal.jvmstat/share/classes/sun/jvmstat/perfdata/monitor/protocol/local/LocalVmManager.java
Outdated
Show resolved
Hide resolved
sspitsyn
left a comment
There was a problem hiding this comment.
Hi Kevin,
This looks okay to me modulo the question from Yasumasa.
Thanks,
Serguei
|
@kevinjwalls 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 15 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 |
YaSuenag
left a comment
There was a problem hiding this comment.
Looks good! Thank you for fixing!
|
/integrate |
|
@kevinjwalls Since your change was applied there have been 30 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 0790e60. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
|
(For the record, the tier1_serviceability tests run OK for me.) |
|
Mailing list message from Laurence Cable on serviceability-dev: and sadly /proc does not support inotify()!!!! On 5/6/21 1:48 PM, Kevin Walls wrote: -------------- next part -------------- |
1 similar comment
|
Mailing list message from Laurence Cable on serviceability-dev: and sadly /proc does not support inotify()!!!! On 5/6/21 1:48 PM, Kevin Walls wrote: -------------- next part -------------- |
This is a merge request to fix the issue where a running jstatd does not see JVMs in docker containers started since the jstatd itself started.
jstatd was using the set of temp directories gathered on startup to scan for VMs, by reading their perfdata file. That includes existing running VMs in docker instances using tmp dirs such as /proc/PID/root/tmp/. But it needs to re-evaluate that set of temp dirs continually to see new VMs in docker containers. Rescanning also means it "forgets" about tmp dirs which have disappeared, for containers that have shutdown, and it will now not be scanning those directories forever.
Have been testing this manually, watching jps connecting to jstatd and show newly created JVMs in docker containers come and go. Running existing tests OK so far.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3908/head:pull/3908$ git checkout pull/3908Update a local copy of the PR:
$ git checkout pull/3908$ git pull https://git.openjdk.java.net/jdk pull/3908/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3908View PR using the GUI difftool:
$ git pr show -t 3908Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3908.diff