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
8254854: [cgroups v1] Metric limits not properly detected on some join controller combinations #809
Conversation
…n controller combinations
👋 Welcome back sgehwolf! A progress list of the required criteria for merging this PR into |
@bobvandette Could you please take a look? It would be much appreciated. |
How does this cgroup file get parsed properly in the hotspot side of things? I don't see more than one controller getting registered per line??? Never mind, I was looking at /proc/cgroup parsing and not /proc/self/cgroup. |
// Ignore subsystems that we don't support | ||
default: | ||
break; | ||
for (String cName: controllerName.split(",")) { |
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.
The previous logic checked for base!=null. Do you think this is no longer necessary?
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.
Isn't this what line 164 does?
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.
Sorry, I missed the fact that line 164 was being retained. I just saw a lot of line removal. Looks good.
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 worries. Thank you for the review!
@jerboaa 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 |
/integrate |
@jerboaa Since your change was applied there have been 19 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit a0b687b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Originally only join controllers of form
cpu,cpuacct
would have been recognized.However, this fails if more controllers are joined at a certain path.
The proposed fix is to be sure to split join controllers on
,
and set the pathaccordingly. Otherwise, the Metrics system might be initialized due to some
non-join controllers, yet the limits for join controllers wouldn't be detected. A
test for this can be added once JDK-8254001 has been implemented.
Testing:
Thoughts?
Progress
Testing
Failed test task
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/809/head:pull/809
$ git checkout pull/809