Overview

If multiple mod-record-specifications instances are started - there could be possible following scenario:

1. Instance #1 start synchronizing specifications

2. Instance #1 sends specification.updated event

3. mod-entities-links consumes specification.updated event and sends 20 specification.update events

4. 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.