[FOLIO-1032] Error setting max JVM heap size based on cgroup limits in Java-based FOLIO docker containers Created: 16/Jan/18 Updated: 06/Sep/19 Resolved: 06/Sep/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | ci | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 hour | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Development Team: | Core: Platform | ||||||||
| Description |
|
Java-based docker images using the fabric8-based base images log the following error in their logs: cat: /sys/fs/cgroup/memory/memory.memsw.limit_in_bytes: No such file or directory Because of this error, containers are unable to properly determine the proper amount of RAM to allocate to the JVM when the container is configured with memory limits at runtime. |
| Comments |
| Comment by John Malconian [ 16/Jan/18 ] |
|
It appears that /sys/fs/cgroup/memory/memory.memsw.limit_in_bytes does not exist on Debian-based host systems. Will need to investigate other options. Possibly an experimental java option called -XX:+UseCGroupMemoryLimitsforHeap. |
| Comment by John Malconian [ 16/Jan/18 ] |
|
ubuntu@ip-10-36-1-185:/proc/sys/kernel$ sudo docker info WARNING: No swap limit support |
| Comment by John Malconian [ 16/Jan/18 ] |
|
Docker spells out the issue with swap limit support and how to enable it in Debian-based distributions pretty clearly here. Our tests systems contain 0 swap. I wonder if enabling swap on these systems is detrimental anyway. If we don't need to swap, we could just use ' /sys/fs/cgroup/memory/memory.limit_in_bytes instead. |