Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Re-assess the container Memory allocation in default LaunchDescriptor

Description

Refer to the ticket Description at FOLIO-2315.

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
David Crossley
changed the StatusNovember 25, 2019 at 3:34 AM
Blocked
Open
David Crossley
updated the Linked IssuesNovember 20, 2019 at 7:59 AM
None
This issue is blocked by CIRCSTORE-173
David Crossley
changed the StatusNovember 20, 2019 at 7:58 AM
Open
Blocked
David Crossley
updated the DescriptionNovember 20, 2019 at 7:58 AM
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). Now that the transition is complete, these levels need to be lowered again. The developers of each back-end module now need to determine the default container memory allocation, and adjust their configuration. At ModuleDescriptor path: $.launchDescriptor.dockerArgs.HostConfig.Memory See [documentation|https://dev.folio.org/guides/module-descriptor/#launchdescriptor-properties]. As noted there, these levels are appropriate for running a basic system such as the "folio-snapshot" reference environment. So this default container memory setting should be as low as possible.
Refer to the ticket Description at FOLIO-2315.
David Crossley
updated the SummaryNovember 20, 2019 at 7:57 AM
Reduce the container Memory allocation in default LaunchDescriptor
Re-assess the container Memory allocation in default LaunchDescriptor
David Crossley
updated the Linked IssuesOctober 28, 2019 at 4:02 AM
None
This issue blocks FOLIO-2315
David Crossley
created the IssueOctober 28, 2019 at 4:02 AM

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 28, 2019 at 4:02 AM
Updated November 25, 2019 at 3:34 AM
Configure
TestRail: Cases
TestRail: Runs

Flag notifications