Closed kchaber closed 4 days ago
Hi @kchaber,
We are always open to a contribution, if you want you can create a PR with a change and we will be more than happy to review it
Depending on the JRE that's used, it should respect JAVA_TOOL_OPTIONS
environment variable for arbitrary settings
Thanks @OneCricketeer for the comment, if @kchaber makes the contribution he should take it into account.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Why was this issue closed? Seems that it's still a concern.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.
Name and Version
bitnami/zookeeper:latest (3.8-debian-11)
What steps will reproduce the bug?
We cannot effectively use
(Initial|Min|Max)RAMPercentage
java arguments as zookeeper container always requires and adds fixed heap size via-Xmx
,-Xms
arguments.The validation is done in the below function inside
scripts/libzookeeper.sh
:What is the expected behavior?
Zookeeper container should not require the
Xmx
,Xms
arguments to be provided inJVMFLAGS
env variable.What do you see instead?
(Initial|Min|Max)RAMPercentage
should be used instead to dynamically allocate heap size based on containercgrups
settings.Additional information
No response