Details
-
Story
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
None
-
-
Folijet Sprint 129
-
5
-
Folijet
-
Lotus R1 2022
Description
There are CPU spikes related to events_cache topic and Kafka cache memory is not released for a long time. Investigate possibility of removing Kafka cache considering results of MODDATAIMP-500 spike. See described problems with Kafka cache MODINV-444 and MODINV-401.
Create necessary stories.
TestRail: Results
Attachments
Issue Links
- defines
-
UXPROD-3261 NFR: R1 2022 Lotus Data import performance work
-
- Closed
-
- is duplicated by
-
MODINV-401 Spike: KafkaCache Memory not released (after a long time)
-
- Closed
-
-
MODINV-444 Spike: CPU spikes related to events_cache topic
-
- Closed
-
- relates to
-
MODINV-588 Implement deduplication for Instances
-
- Closed
-
-
MODINV-589 Implement deduplication for Holdings
-
- Closed
-
-
MODINV-590 Implement deduplication for Items
-
- Closed
-
-
MODINV-591 Implement deduplication for Authorities
-
- Closed
-
-
MODINV-598 Remove Kafka cache from update handlers
-
- Closed
-
-
MODINV-603 Remove Kafka cache by handling Constraint Violation Exceptions for DataImportKafkaHandler
-
- Closed
-
-
MODSOURMAN-638 Remove Kafka cache by handling Constraint Violation Exceptions for StoreRecordsChunksKafkaHandler
-
- Closed
-
-
MODSOURMAN-639 Improve performance of saving journal records during import
-
- Closed
-
-
MODSOURMAN-640 Remove Kafka cache by handling Constraint Violation Exceptions for DataImportJournalKafkaHandler
-
- Closed
-
-
MODSOURMAN-641 Remove Kafka cache by handling Constraint Violation Exceptions
-
- Closed
-
-
MODSOURMAN-642 SPIKE: Investigate possibilities to combine job_execution, job_execution_progress and job_monitoring tables
-
- Draft
-
-
MODSOURMAN-668 Restructure job_execution_progress table for DataImportKafkaHandler
-
- Closed
-