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
Use requests instead of limits for determining Xmx #2225
Conversation
How have you tested this? |
183deb4
to
c39e40d
Compare
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 -Xmx
and -Xms
have IMHO no direct relationship to the request and limit. Request is requested (and guaranteed memory) where as limit is basically a burst memory which might or might not be available.
cluster-operator/src/main/java/io/strimzi/operator/cluster/model/AbstractModel.java
Outdated
Show resolved
Hide resolved
cluster-operator/src/main/java/io/strimzi/operator/cluster/model/AbstractModel.java
Outdated
Show resolved
Hide resolved
cluster-operator/src/main/java/io/strimzi/operator/cluster/model/AbstractModel.java
Outdated
Show resolved
Hide resolved
41bd2a4
to
a79bc5c
Compare
@stanlyDoge Could you add this to the CHANGELOG and make it clear what exactly changed and how does it impact the users?? |
Signed-off-by: Stanislav Knot <sknot@redhat.com>
955668a
to
cfc2244
Compare
cfc2244
to
2176513
Compare
Signed-off-by: Stanislav Knot sknot@redhat.com
Type of change
Description
Fixes #2203
It was not clear for me, how the setting of
ENV_VAR_DYNAMIC_HEAP_MAX
worked with the user's value. Please take a look and feel free to describe how it should work.Checklist
./design