All work
1 of 1
specification.update consumer ignores first messages when scaled
Done
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
Checklist
hideDetails
Assignee
Viacheslav KolesnykViacheslav KolesnykReporter
Viacheslav KolesnykViacheslav KolesnykLabels
Priority
P2Story Points
0.5Sprint
NoneDevelopment Team
SpitfireFix versions
Release
Sunflower (R1 2025)RCA Group
Implementation coding issueTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Viacheslav Kolesnyk
Viacheslav KolesnykReporter
Viacheslav Kolesnyk
Viacheslav KolesnykLabels
Priority
P2Story Points
0.5
Sprint
None
Development Team
Spitfire
Fix versions
Release
Sunflower (R1 2025)
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 18, 2025 at 11:57 AM
Updated March 3, 2025 at 6:35 PM
Resolved February 24, 2025 at 5:15 PM
Activity
Show:
Valery_PilkoFebruary 21, 2025 at 7:26 AM
Verified in the scope of
Overview
If multiple mod-record-specifications instances are started - there could be possible following scenario:
Instance #1 start synchronizing specifications
Instance #1 sends specification.updated event
mod-entities-links consumes specification.updated event and sends 20 specification.update events
Instance #2 starts consumers and founds no commited offset for specification.update so by default it set’s it to LATEST, which is 20, ignoring earlier sent messages
Approach
Set consumer auto.offset.reset for specification.update as EARLIEST.