Details
-
Umbrella
-
Status: Blocked (View Workflow)
-
TBD
-
Resolution: Unresolved
-
None
-
-
CP: sprint 75, CP: sprint 76, DevOps: Sprint 95
-
3
-
Core: Platform
Description
During the transition to using settings for "container memory" in each back-end module's default LaunchDescriptor (FOLIO-1729 FOLIO-2185) instead of using folio-ansible group_vars to specify -Xmx Java option (FOLIO-2241 FOLIO-2242), we needed to temporarily raise the container memory allocation to 130% of the old -Xmx setting (FOLIO-2250).
Subsequently, FOLIO-2358 is now in progress to use new JVM features to manage container memory. After each module is upgraded (see each ticket linked from FOLIO-2358) then it will be utilising 66% of the LaunchDescriptor "Memory" setting for the Java heap allocation, leaving the remainder for other stuff.
So after each is upgraded, then the next step is for the developers of each back-end module to determine the default container Memory allocation, and adjust their configuration.
At ModuleDescriptor path: $.launchDescriptor.dockerArgs.HostConfig.Memory
See documentation.
As noted there, these levels are appropriate for running a basic system such as the "folio-snapshot-load" reference environment and the Vagrant VMs. So this default container memory setting should be as low as possible.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
CIRC-529 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
CIRCSTORE-166 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
EDGOAIPMH-33 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
EDGORDERS-18 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
EDGPATRON-24 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
EDGRESOLV-7 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
EDGRTAC-15 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
ERM-536 mod-agreements Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
FOLIO-2334 Spike: Investigate using JVM features to manage container memory
-
- Closed
-
-
MODAFILT-10 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODAT-55 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODAUD-5 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODCAL-55 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODCAT-142 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODCONF-34 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODCR-4 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODCXEKB-99 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODCXINV-42 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODCXMUX-56 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODDATAIMP-219 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODDICONV-80 Reduce the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODDICONV-83 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODEMAIL-26 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODEUS-41 mod-erm-usage Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODEUS-51 mod-erm-usage-harvester Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODEVENTC-13 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODFEE-15 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODFIN-80 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODFISTO-53 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODGOBI-93 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODINV-169 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODINVOICE-111 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODINVOSTO-43 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODINVSTOR-384 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODKBEKBJ-326 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODLOGIN-120 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODLOGSAML-49 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODNOTES-133 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODNOTIFY-56 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODOAIPMH-77 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODORDERS-325 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODORDSTOR-117 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODORGSTOR-49 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODPATRON-33 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODPERMS-69 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODPWD-25 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODRTAC-21 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODSENDER-22 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODSOURCE-80 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODSOURMAN-223 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODTAG-31 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Closed
-
-
MODTEMPENG-32 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODUIMP-11 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODUSERBL-81 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
MODUSERS-156 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
-
SIP2-74 Re-assess the container Memory allocation in default LaunchDescriptor
-
- Open
-
- relates to
-
FOLIO-2358 Use JVM features (UseContainerSupport, MaxRAMPercentage) to manage container memory
-
- Closed
-
-
FOLIO-1729 Use container memory limits to manage memory in reference environments
-
- Closed
-
-
FOLIO-2250 RMB modules crash on tenant init with updated LaunchDescriptor
-
- Closed
-