Re-assess the memory allocation in default LaunchDescriptor of each back-end ModuleDescriptor
Description
Environment
None
Potential Workaround
None
is blocked by
Checklist
hideTestRail: Results
Activity
Show:
David Crossley November 2, 2019 at 1:09 AM
As notified above, please do not proceed until we have investigated which is scheduled for next Sprint 76.
Oleksii Kuzminov October 30, 2019 at 9:48 AM
We don't merge changes yet. So we will just postpone them
Ann-Marie Breaux October 30, 2019 at 5:50 AM
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:
Ann-Marie Breaux October 30, 2019 at 5:43 AM
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.
David Crossley October 30, 2019 at 5:30 AMEdited
Please ask teams to hold off with making any configuration changes. We are investigating another option that might assist with this configuration.
Details
Details
Assignee
David Crossley
David CrossleyReporter
David Crossley
David CrossleyLabels
Priority
TBDStory Points
3
Sprint
None
Development Team
Core: Platform
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created October 22, 2019 at 8:17 AM
Updated August 10, 2020 at 1:20 PM
TestRail: Cases
TestRail: Runs
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.