Use JVM features to manage container memory
Description
Checklist
hideTestRail: Results
Activity

steve.osguthorpe December 4, 2019 at 3:07 PM
@David Crossley Should be sorted now.

steve.osguthorpe December 4, 2019 at 10:48 AM
Sorry david I actually had it fixed properly on another branch but had to sort out a different error and hastily added the change while I was in the file.

David Crossley December 4, 2019 at 12:39 AM
I see from yesterday's mod-agreements/pull/223 that you modified the JAVA_OPTIONS. However it still has the old folio base docker image (with lesser java version). So these will not have the desired effect.
See the steps at FOLIO-2358.
Consequently i have not yet done the step #3 of that list.

David Crossley November 29, 2019 at 12:58 AM
There is further discussion on the ticket FOLIO-2334, so that we can keep the notes focussed.

steve.osguthorpe November 28, 2019 at 1:28 PM
@David Crossley Metaspace is not affected by these settings, only heap. So the percentage of heap needed is not directly proportional for applications. We can set it for the value detailed in the module descriptor but decreasing container memory would result in an OOM kill because of exhausted metaspace, even thought the Heap might be ample.
Details
Details
Components
Assignee

Reporter

Update the module's Dockerfile and LaunchDescriptor as explained in FOLIO-2358.