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:

Marc Johnson August 26, 2020 at 4:01 PM

I believe the memory allocation for mod-circulation was recently reviewed following integration with pub-sub which might mean this is now redundant

David Crossley August 17, 2020 at 2:02 AM

I have no idea, and it is not up to me. My task was to create the mechanism to declare this memory level in a module's LaunchDescriptor and using it in our infrastructure, and to add FOLIO-2315 to encourage the developers of each back-end module to decide the appropriate level. Sorry, i cannot help further.

Marc Johnson August 13, 2020 at 11:27 AM

Does this still apply given that I believe there have been recent changes to the memory allocation for mod-circulation (since integrating with pub-sub)?

Won't Do

Details

Assignee

Reporter

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs
Created October 28, 2019 at 4:00 AM
Updated August 26, 2020 at 4:01 PM
Resolved August 26, 2020 at 4:01 PM
Configure
TestRail: Cases
TestRail: Runs