Details
-
New Feature
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
None
-
customfield_11100 30986
-
CP: sprint 77, CP: sprint 78
-
8
-
Core: Platform
Description
To enable the JVM to use defaults in a container environment, Java 10 introduced "UseContainerSupport" and that was backported to Java 8 (8u191+). Use that in conjunction with "MaxRAMPercentage". These features were investigated in FOLIO-2334.
Now update every back-end module to utilise these settings. Specifically:
- In its Dockerfile, use the new JVM docker base image folioci/alpine-jre-openjdk8:latest
- In its ModuleDescriptor at the LaunchDescriptor, use this setting for JAVA_OPTIONS: "-XX:MaxRAMPercentage=66.0"
- After merge, then follow-up to remove its default settings from folio-ansible group_vars.
See enhanced documentation (FOLIO-2357) at https://dev.folio.org/guides/module-descriptor/#launchdescriptor-properties
There will be linked tickets for each back-end module.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
CIRC-565 Use JVM features to manage container memory
-
- Closed
-
-
CIRCSTORE-173 Use JVM features to manage container memory
-
- Closed
-
-
EDGOAIPMH-34 Use JVM features to manage container memory
-
- Closed
-
-
EDGORDERS-20 Use JVM features to manage container memory
-
- Closed
-
-
EDGPATRON-25 Use JVM features to manage container memory
-
- Closed
-
-
EDGRESOLV-8 Use JVM features to manage container memory
-
- Closed
-
-
EDGRTAC-18 Use JVM features to manage container memory
-
- Closed
-
-
ERM-583 Use JVM features to manage container memory
-
- Closed
-
-
ERM-638 Use JVM features to manage container memory
-
- Closed
-
-
FOLIO-2334 Spike: Investigate using JVM features to manage container memory
-
- Closed
-
-
MODAFILT-11 Use JVM features to manage container memory
-
- Closed
-
-
MODAT-57 Use JVM features to manage container memory
-
- Closed
-
-
MODAUD-6 Use JVM features to manage container memory
-
- Closed
-
-
MODCAL-60 Use JVM features to manage container memory
-
- Closed
-
-
MODCAT-145 Use JVM features to manage container memory
-
- Closed
-
-
MODCONF-41 Use JVM features to manage container memory
-
- Closed
-
-
MODCR-7 Use JVM features to manage container memory
-
- Closed
-
-
MODCXEKB-101 Use JVM features to manage container memory
-
- Closed
-
-
MODCXINV-43 Use JVM features to manage container memory
-
- Closed
-
-
MODCXMUX-58 Use JVM features to manage container memory
-
- Closed
-
-
MODDATAIMP-222 Use JVM features to manage container memory
-
- Closed
-
-
MODDICONV-84 Use JVM features to manage container memory
-
- Closed
-
-
MODEMAIL-30 Use JVM features to manage container memory
-
- Closed
-
-
MODEUS-42 mod-erm-usage Use JVM features to manage container memory
-
- Closed
-
-
MODEVENTC-16 Use JVM features to manage container memory
-
- Closed
-
-
MODFEE-18 Use JVM features to manage container memory
-
- Closed
-
-
MODFIN-95 Use JVM features to manage container memory
-
- Closed
-
-
MODFISTO-66 Use JVM features to manage container memory
-
- Closed
-
-
MODGOBI-95 Use JVM features to manage container memory
-
- Closed
-
-
MODINV-175 Use JVM features to manage container memory
-
- Closed
-
-
MODINVOICE-115 Use JVM features to manage container memory
-
- Closed
-
-
MODINVOSTO-44 Use JVM features to manage container memory
-
- Closed
-
-
MODINVSTOR-396 Use JVM features to manage container memory
-
- Closed
-
-
MODKBEKBJ-338 Use JVM features to manage container memory
-
- Closed
-
-
MODLOGIN-121 Use JVM features to manage container memory
-
- Closed
-
-
MODLOGSAML-53 Use JVM features to manage container memory
-
- Closed
-
-
MODNOTES-135 Use JVM features to manage container memory
-
- Closed
-
-
MODNOTIFY-57 Use JVM features to manage container memory
-
- Closed
-
-
MODOAIPMH-80 Use JVM features to manage container memory
-
- Closed
-
-
MODORDERS-339 Use JVM features to manage container memory
-
- Closed
-
-
MODORDSTOR-123 Use JVM features to manage container memory
-
- Closed
-
-
MODORGSTOR-51 Use JVM features to manage container memory
-
- Closed
-
-
MODPATRON-35 Use JVM features to manage container memory
-
- Closed
-
-
MODPERMS-72 Use JVM features to manage container memory
-
- Closed
-
-
MODPUBSUB-62 Add new LaunchDescriptor and use new base docker image
-
- Closed
-
-
MODPWD-27 Use JVM features to manage container memory
-
- Closed
-
-
MODRTAC-24 Use JVM features to manage container memory
-
- Closed
-
-
MODSENDER-23 Use JVM features to manage container memory
-
- Closed
-
-
MODSOURCE-82 Use JVM features to manage container memory
-
- Closed
-
-
MODSOURMAN-234 Use JVM features to manage container memory
-
- Closed
-
-
MODTAG-33 Use JVM features to manage container memory
-
- Closed
-
-
MODTEMPENG-35 Use JVM features to manage container memory
-
- Closed
-
-
MODUIMP-12 Use JVM features to manage container memory
-
- Closed
-
-
MODUSERBL-82 Use JVM features to manage container memory
-
- Closed
-
-
MODUSERS-160 Use JVM features to manage container memory
-
- Closed
-
-
SIP2-75 Use JVM features to manage container memory
-
- Closed
-
- relates to
-
FOLIO-2367 Remove openjdk8-jre-alpine
-
- Closed
-
-
FOLIO-2394 Update folio-ansible group_vars to remove remaining over-ride docker_env
-
- Closed
-
-
FOLIO-1544 switch to Alpine to shrink docker containers
-
- Closed
-
-
FOLIO-2315 Re-assess the memory allocation in default LaunchDescriptor of each back-end ModuleDescriptor
-
- Blocked
-
-
FOLIO-2357 Enhance dev.f.o docs regarding default LaunchDescriptor, docker image, Memory, Java options
-
- Closed
-