Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Complexity

S, M, L, XL, XXL

Table


CategoryProblem definitionBusiness impactProposed solution

Priority

DEV

Priority

PO

ComplexityExisting Jira item(s)Current feature(s)Final feature (s)
1PerformanceKafka producer closed after sendingLow performance of import

Create pool of active producers. Start pool on module launch, close on shutdown. Reuse connections.

Add max/min pool sizes.

High
L

Jira Legacy
server

FOLIO Issue Tracker

System Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-499

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


2
WARN message when no handler foundnone

Do not subscribe to messages you're not going to process

OR

Lower log lever for this type of messages

Low
S

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURCE-340

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


3Stability/Reliability

Race condition on start (Kafka consumers start working before DB is configured)

OR

Periodical DB shutdown after SRS restart. Jobs get stuck if not able to update status in DB (messages ACKed even if we could not process them)

Imports might get stuck on module restart

Need investigation / check

Investigate the issue with DB (possible OOM on PG server)


Mid

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURCE-339

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


4

Performance

Stability/Reliability

High CPU/Memory consumption on modulesLow performance of import. Higher costs for hosting

Significantly decrease size of payload:

  1. Remove immutable parts. Instead fetch them on demand and cache locally for reuse.
  2. Change message handling mechanism (currently relies on pt1 - profile) (optional)
  3. Move archiving to Kafka instead of module level
High
XXL

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-439

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-519

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-405

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-408

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-460

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINVOICE-251

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINVOICE-252

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODPUBSUB-167

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURCE-286

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURCE-290

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-463

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-464

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-465

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-466

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-468

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-469

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-474

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-519


Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


5PerformanceKafka cache resource consumptionLow performance of import. Higher costs of hosting.Remove Kafka cache. Modules that do not do persistent changes will sometimes (on duplicates read) do unnecessary calls. Can be optimized further upon adding distributed in-memory cache (ex hazelcast) (blocked by 6)Mid
M

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-444

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-401


Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


6Stability/ReliabilityDuplicates created upon importData inconsistency on import.Make consumers behave idempotent. Add pass-through identifier to de-duplicate messages. High
XL

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-474

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-440

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-491

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-495



Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


7Stability/ReliabilityKafka consumers stop reading messages eventually, breaking job progress until module restart.Imports eventually get stuck until module restartNeed investigationHigh
?

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-417

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


8Code qualityTest coverage is not high enough (Unit)Higher amount of bugsWrite more testsMid
S

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODPUBSUB-168


Jira Legacy
server

FOLIO Issue Tracker

System Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-

3135

2697


9Code qualityTest coverage is not high enough (Karate)Higher amount of bugsWrite more tests (define test cases)Mid
L

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-2697

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-2697


10Stability/Reliabilitymod-data-import stores input file in memory, limiting size of uploaded file and possibly having oomData import file size is limitedSplit to chunks, put to database, work with database/temp storage. Partially done (to be investigated)Mid
L

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-390

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-392

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-465

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


11PerformanceData import impacts other processesSlower response of system during data import

Need investigation (possible solution - configure rate limiter)

Relates to number 4




no ticket

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


12PerformanceHigh resource consumption to get job(s) status/progressSlow performance of import and landing page.Add some kind of caching for progress tracking (database or in-memory)Low
S

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-469

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUIDATIMP-918

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


13Stability/ReliabilitySRS can fail when processing messageduring import
Import can end up creating some instances but not creating holdings/items for some MARC records

Generate "INSTANCE CREATED" from mod-inventory. Consume in SRS to update HRID in BIB and in INVENTORY to continue processing.


Remove unnecessary topics (* ready for post processing and hrid set)

Mid
L

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-500

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


14Stability/Reliability

If we have infrastructure issue (like DB not available, module being restarted or network failure), we are sending DI_ERROR instead of retrying

Records that can potentially be processed during import are not processed if we have temporary infrastructure issues (DB down, network connectivity loss, etc)

Do not ACK messages in Kafka if there's not a logic, but infrastructure error/exception. Split failed processing results into 2 categories:

  1. IO errors - do not ack. retry until fixed
  2. Business logic - DI_ERROR and Ack current message
Mid

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODDATAIMP-501

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


15
Consumer gets disconnected from Kafka clusterJobs get stuck until module restartNeed investigationMid

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODINV-417

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


16
De-duplication of status messages for progress barProgress bar might display incorrect progressDe-duplicate status messages per-record while tracking progressMid
L (depends on 12)

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyMODSOURMAN-522

Jira Legacy
server

FOLIO Issue Tracker

System Jira
serverId

6ccf3fe4

01505d01-

3301

b853-

368a

3c2e-

983e

90f1-

20c466b11a49

ee9b165564fc
keyUXPROD-3135


Filters

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
columnIdsissuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQuerylabels in (di-configuration, di-data-integrity, di-performance, di-functional-bug, di-change-request, di-architecture, di-other) and resolution in (Unresolved) ORDER BY status DESC
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc

Issues to potentially remove from scope

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODDATAIMP-410

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODDATAIMP-430

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODDATAIMP-444

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODSOURCE-300

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODSOURMAN-481

Jira Legacy
serverFOLIO Issue TrackerSystem Jira
serverId6ccf3fe401505d01-3301b853-368a3c2e-983e90f1-20c466b11a49ee9b165564fc
keyMODSOURMAN-521

Links

Data Import Observations for Improvements