[FOLIO-2315] Re-assess the memory allocation in default LaunchDescriptor of each back-end ModuleDescriptor Created: 22/Oct/19  Updated: 10/Aug/20

Status: Blocked
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Umbrella Priority: TBD
Reporter: David Crossley Assignee: David Crossley
Resolution: Unresolved Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by EDGPATRON-24 Re-assess the container Memory alloca... Open
is blocked by MODINVOICE-111 Re-assess the container Memory alloca... Open
is blocked by CIRCSTORE-166 Re-assess the container Memory alloca... Open
is blocked by EDGORDERS-18 Re-assess the container Memory alloca... Open
is blocked by MODAFILT-10 Re-assess the container Memory alloca... Open
is blocked by MODAT-55 Re-assess the container Memory alloca... Open
is blocked by MODAUD-5 Re-assess the container Memory alloca... Open
is blocked by MODCONF-34 Re-assess the container Memory alloca... Open
is blocked by MODCR-4 Re-assess the container Memory alloca... Open
is blocked by MODEMAIL-26 Re-assess the container Memory alloca... Open
is blocked by MODEVENTC-13 Re-assess the container Memory alloca... Open
is blocked by MODFEE-15 Re-assess the container Memory alloca... Open
is blocked by MODFIN-80 Re-assess the container Memory alloca... Open
is blocked by MODFISTO-53 Re-assess the container Memory alloca... Open
is blocked by MODGOBI-93 Re-assess the container Memory alloca... Open
is blocked by MODINV-169 Re-assess the container Memory alloca... Open
is blocked by MODINVOSTO-43 Re-assess the container Memory alloca... Open
is blocked by MODINVSTOR-384 Re-assess the container Memory alloca... Open
is blocked by MODLOGIN-120 Re-assess the container Memory alloca... Open
is blocked by MODLOGSAML-49 Re-assess the container Memory alloca... Open
is blocked by MODNOTIFY-56 Re-assess the container Memory alloca... Open
is blocked by MODOAIPMH-77 Re-assess the container Memory alloca... Open
is blocked by MODORDERS-325 Re-assess the container Memory alloca... Open
is blocked by MODORDSTOR-117 Re-assess the container Memory alloca... Open
is blocked by MODORGSTOR-49 Re-assess the container Memory alloca... Open
is blocked by MODPERMS-69 Re-assess the container Memory alloca... Open
is blocked by MODSENDER-22 Re-assess the container Memory alloca... Open
is blocked by MODTEMPENG-32 Re-assess the container Memory alloca... Open
is blocked by MODUIMP-11 Re-assess the container Memory alloca... Open
is blocked by MODUSERBL-81 Re-assess the container Memory alloca... Open
is blocked by MODUSERS-156 Re-assess the container Memory alloca... Open
is blocked by SIP2-74 Re-assess the container Memory alloca... Open
is blocked by FOLIO-2334 Spike: Investigate using JVM features... Closed
is blocked by MODDICONV-83 Re-assess the container Memory alloca... Closed
is blocked by EDGOAIPMH-33 Re-assess the container Memory alloca... Closed
is blocked by MODDATAIMP-219 Re-assess the container Memory alloca... Closed
is blocked by MODDICONV-80 Reduce the container Memory allocatio... Closed
is blocked by MODKBEKBJ-326 Re-assess the container Memory alloca... Closed
is blocked by MODSOURCE-80 Re-assess the container Memory alloca... Closed
is blocked by MODSOURMAN-223 Re-assess the container Memory alloca... Closed
is blocked by MODTAG-31 Re-assess the container Memory alloca... Closed
is blocked by CIRC-529 Re-assess the container Memory alloca... Closed
is blocked by EDGRESOLV-7 Re-assess the container Memory alloca... Closed
is blocked by EDGRTAC-15 Re-assess the container Memory alloca... Closed
is blocked by ERM-536 mod-agreements Re-assess the containe... Closed
is blocked by MODCAL-55 Re-assess the container Memory alloca... Closed
is blocked by MODCAT-142 Re-assess the container Memory alloca... Closed
is blocked by MODCXEKB-99 Re-assess the container Memory alloca... Closed
is blocked by MODCXINV-42 Re-assess the container Memory alloca... Closed
is blocked by MODCXMUX-56 Re-assess the container Memory alloca... Closed
is blocked by MODEUS-41 mod-erm-usage Re-assess the container... Closed
is blocked by MODEUS-51 mod-erm-usage-harvester Re-assess the... Closed
is blocked by MODNOTES-133 Re-assess the container Memory alloca... Closed
is blocked by MODPATRON-33 Re-assess the container Memory alloca... Closed
is blocked by MODPWD-25 Re-assess the container Memory alloca... Closed
is blocked by MODRTAC-21 Re-assess the container Memory alloca... Closed
Relates
relates to FOLIO-2358 Use JVM features (UseContainerSupport... Closed
relates to FOLIO-1729 Use container memory limits to manage... Closed
relates to FOLIO-2250 RMB modules crash on tenant init with... Closed
Sprint: CP: sprint 76, DevOps: Sprint 95, CP: sprint 75
Story Points: 3
Development Team: Core: Platform

 Description   

During the transition to using settings for "container memory" in each back-end module's default LaunchDescriptor ( FOLIO-1729 Closed FOLIO-2185 Closed ) instead of using folio-ansible group_vars to specify -Xmx Java option ( FOLIO-2241 Closed FOLIO-2242 Closed ), we needed to temporarily raise the container memory allocation to 130% of the old -Xmx setting ( FOLIO-2250 Closed ).

Subsequently, FOLIO-2358 Closed 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 Closed ) 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.



 Comments   
Comment by David Crossley [ 30/Oct/19 ]

Please ask teams to hold off with making any configuration changes. We are investigating another option that might assist with this configuration. FOLIO-2334 Closed

Comment by Ann-Marie Breaux (Inactive) [ 30/Oct/19 ]

Oleksii Kuzminov See David's comment above. In the linked issues, I see we have stories for 2 of our MOD apps in code review, but several others still Open.

Comment by Ann-Marie Breaux (Inactive) [ 30/Oct/19 ]

David Crossley If some changes have already been made (MODDICONV closed, MODSOURMAN, MODSOURCE in code review), do those need to be reverted, or can they just stay as they are?

cc: Oleksii Kuzminov

Comment by Oleksii Kuzminov [ 30/Oct/19 ]

Ann-Marie Breaux We don't merge changes yet. So we will just postpone them

Comment by David Crossley [ 02/Nov/19 ]

As notified above, please do not proceed until we have investigated FOLIO-2334 Closed which is scheduled for next Sprint 76.

Generated at Thu Feb 08 23:19:46 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.