Details
-
Bug
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
2.0.0
-
customfield_11100 48274
-
5
-
Folijet Support
-
R2 2021 Hot Fix #3
-
Yes
-
Juniper hotfix reconfirmed by CPT in the Slack release_bug_triage channel 4 Oct 2021.
-
Implementation coding issue
Description
Overview:
When uploading a MARC file in an Iris environment, mod-data-import seems to use up all the memory necessary to process the file, but after the test is over, the memory does not get released. This causes the container to crash because it runs out of memory on subsequent imports. This situation is reproduced on the Vagrant Testing box too (see attachment).
Steps to Reproduce:
Upload a moderate file multiple times (500K records). Depending on the size of the file and the memory allocated to the container, the container will crash after 2 or more uploads. Can also observe the container's memory graphs on Cloudwatch or similar tools.
Expected Results:
Memory is released after an import, multiple subsequent uploads of the same file will not crash the system.
Actual Results:
See above
Interested parties:
OleksiiKuzminov abreaux Kateryna Senchenko
TestRail: Results
Attachments
Issue Links
- blocks
-
MODDATAIMP-560 Release v2.1.3 (R2 Juniper Hot Fix #3)
-
- Closed
-
- defines
-
UXPROD-3193 NFR: R3 2021 Kiwi Data import Stability/Reliability work
-
- Closed
-
- has to be done after
-
MODDATAIMP-489 Test new shared Rancher env
-
- Closed
-
- relates to
-
MODDATAIMP-390 Spike: Memory not released after import
-
- Closed
-