-
Notifications
You must be signed in to change notification settings - Fork 14.5k
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
Clarify cgroupsV2 Java statements #40189
Conversation
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.
@bobbypage & @mrunalp, thoughts on this?
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site settings. |
/lgtm |
LGTM label has been added. Git tree hash: 931d335fe10181f414f55006db1df025f0246ed1
|
* If you deploy Java applications with the JDK, prefer to use JDK 11.0.16 and | ||
later or JDK 15 and later, which [fully support cgroup v2](https://bugs.openjdk.org/browse/JDK-8230305). | ||
* If you deploy Java applications, prefer to use versions which fully support cgroup v2: | ||
* [HotSpot](https://bugs.openjdk.org/browse/JDK-8230305): jdk8u372, 11.0.16, 15 and 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.
Should we say Hotspot / Open JDK
?
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.
I've always found the term OpenJDK ambiguous in JVM diagnostic situations because, for example, IBM Semeru Runtimes also uses OpenJDK for its JDK implementation, but the issue here isn't about the JDK classes but rather about the JVM which does the cgroups detection (IBM's JVM is called J9). However, OpenJDK is also commonly used to refer to the whole package of JDK and HotSpot JVM, so I can see an argument for both sides. Do you happen to know anyone from Oracle that could comment?
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.
/cc @jmtd, I see you added the backport, do you have any thoughts here?
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.
It's a tricky one. I'd definitely choose to include "OpenJDK" in the wording, because we know that the support has landed there, and can't speak more broadly about downstream vendors' versions (Vendors are capable of removing or disabling features as well as adding them: although it's very unlikely for that to happen for a feature like this). As for mentioning HotSpot, I'd argue it's less important: the majority of OpenJDK users are using HotSpot, but many of them may be unfamiliar with the terminology; on the other hand, for users who don't use HotSpot, such as OpenJ9 users, I'd wager they are more likely to be aware that they can't take a statement about OpenJDK on face value for their situation.
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.
As an OpenJ9 project lead, I'm not sure it matters in this case which term is used given the next two lines refer to Semeru and IBM Java as both are OpenJ9-based distributions.
Generally, we prefer Hotspot is used for Hotspot-specific behaviours as OpenJDK is frequently an umbrella term for all distributions which ship OpenJDK class libraries
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.
Okay, so correct me if I misunderstood, but it sounds like the preference is to just write "OpenJDK / HotSpot". I'll update the commit and squash soon (-ish; have a few higher priority things right now).
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.
Thanks @jmtd and @DanHeidinga for the feedback!
Ah, yes, I wasn't aware of that page. I'll update that as well. |
Signed-off-by: Kevin Grigorenko <[email protected]>
Looks great, thanks for the update! /lgtm |
LGTM label has been added. Git tree hash: a0489ba992ed921c45fc4b93a29cd043fc038a01
|
/assign @sftim |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kbhawkey The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
content/zh-cn/blog/_posts/2022-08-31-cgroupv2-ga.md
which would be nice to update as well.Although this is an older blog post, people still use and reference it.