Uploaded image for project: 'mod-data-import-converter-storage'
  1. mod-data-import-converter-storage
  2. MODDICONV-80

Reduce the container Memory allocation in default LaunchDescriptor

    XMLWordPrintable

Details

    • EPAM BatchLoader Sprint 28
    • 0.5
    • Folijet

    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).

      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.

      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.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                ruslan_lavrov Ruslan Lavrov
                dcrossley David Crossley
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases