You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The helloworld app (not operator) is running into severe memory pressure on my machine, often getting OOMkilled under the default resource settings (256MiB memory limit).
Possible solution
We should be setting the Java memory limit flag (-Xmx), but even then the memory usage seems far higher than I would have expected... It's also suspicious how inconsistent my experience is with @razvan's.
Additional context
No response
Environment
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.31.0+k3s1
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered:
* chore: bump rust version in stackable base image
* cargo update
* remove unused env var
* cargo update
* reintroduce the CONTAINERDEBUG_LOG_DIRECTORY env var
* Bring Cargo.nix up to date
* Add JVM memory limit to work around #147
* Split out containerdebug probe into a separate test step
This should help reduce the amount of spam while checking other assertions
* Don't print the full containerdebug output
---------
Co-authored-by: Natalie Klestrup Röijezon <[email protected]>
Affected Stackable version
main
Affected Hello World version
main
Current and expected behavior
The helloworld app (not operator) is running into severe memory pressure on my machine, often getting OOMkilled under the default resource settings (256MiB memory limit).
Possible solution
We should be setting the Java memory limit flag (-Xmx), but even then the memory usage seems far higher than I would have expected... It's also suspicious how inconsistent my experience is with @razvan's.
Additional context
No response
Environment
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.31.0+k3s1
Would you like to work on fixing this bug?
None
The text was updated successfully, but these errors were encountered: