Skip to content

James: unset JAVA_TOOL_OPTIONS env variable when running james-cli#2403

Merged
Arsnael merged 1 commit into
apache:masterfrom
quantranhong1999:fix-k8s-james-cli-memory-constraint
Sep 10, 2024
Merged

James: unset JAVA_TOOL_OPTIONS env variable when running james-cli#2403
Arsnael merged 1 commit into
apache:masterfrom
quantranhong1999:fix-k8s-james-cli-memory-constraint

Conversation

@quantranhong1999
Copy link
Copy Markdown
Member

GIVEN I run james-cli in kubernetes
THEN the pod crashes and reboots

Because the james-cli runs JVM it catches the environment variables set by James. As such it always pretouch 3GB of RAM. When added to memory consumed by James it exceeds the limit and pod get's OOM-killed.

GIVEN I run james-cli in kubernetes
THEN the pod crashes and reboots

Because the james-cli runs JVM it catches the environment variables set by James.
As such it always pretouch 3GB of RAM. When added to memory consumed by James it exceeds the limit and pod get's OOM-killed.
@Arsnael
Copy link
Copy Markdown
Contributor

Arsnael commented Sep 9, 2024

Is the CI not picking up the newly opened PRs today?

@quantranhong1999
Copy link
Copy Markdown
Member Author

Is the CI not picking up the newly opened PRs today?

It seems so...

@Arsnael
Copy link
Copy Markdown
Contributor

Arsnael commented Sep 10, 2024

Seems it did meanwhile :) Merging

@Arsnael Arsnael merged commit 8c7ad74 into apache:master Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants