Details
-
Task
-
Status: Closed (View Workflow)
-
P2
-
Resolution: Done
-
None
-
-
Folijet Sprint 136
-
1
-
Folijet
-
Lotus (R1 2022) Bug Fix
-
Not a bug
Description
After DI of 100K records on perf-rancher by "PTF - Create 2" profile we found 5 error messages:
"org.folio.kafka.exception.DuplicateEventException: Duplicated event by Instance id: a574d3b4-d0ea-4a21-9c23-0c6d0e3ef681"
"DuplicateEventException: Duplicated event by Holding id: c6831812-0eb2-45a3-8902-af360362f81a"
"DuplicateEventException: Duplicated event by Instance id: 2d9c9bfe-728c-4f06-9199-43f46a292e17"
"DuplicateEventException: Duplicated event by Item id: 1bdd5a97-63e9-4927-a4ba-2d47a2037e1a"
"DuplicateEventException: Duplicated event by Item id: 13d25dbf-81e6-46d9-81ff-d0036f33bf4f"
This is normal behavior for repeated kafka packages, but DI_ERROR should not be sent.
Expected result:
DI_ERROR should not be sent after org.folio.kafka.exception.DuplicateEventException
Actual result:
We received DuplicateEventException in DI journal.
TestRail: Results
Attachments
Issue Links
- blocks
-
MODDICORE-256 Release v3.3.2 (R1 Lotus Bugfix)
-
- Closed
-
- defines
-
UXPROD-3262 NFR: Data Import R1 2022 Lotus Technical, NFR, & Misc work
-
- Closed
-
- has to be done before
-
MODINV-673 Update data-import-processing-core dependency to v3.3.2
-
- Closed
-
- is cloned by
-
MODDICORE-260 Check and fix the sending of DI_ERROR after appears DuplicateEventException - Morning Glory
-
- Closed
-
- relates to
-
MODINV-646 Add logic to skip sending DI_ERROR from mod-inventory in case for duplicates - Lotus Bugfix
-
- Closed
-