1
83%
master: 94%

Ran 07 Feb 2025 01:15PM UTC

Files 183

Run time 4s

Badge

Embed ▾

Committed 07 Feb 2025 01:04PM UTC coverage: 83.255% (+0.1%) from 83.115%

Job # 13200507137.1

Build Type

Pull #720

Committed by

migesok

Commit Message

Add ReplicatedOffsetNotifier callback

Current recovery logic doesn't scale when the volume of events is large,
because clients have to consume all the events on all the app nodes.
Additionally, current logic creates Kafka consumers on-demand,
which is a heavy operation. This consumer creation happens in spikes,
when replicator is running late, and affects client applications stability.

Introducing a side channel for notifications about replication progress
will allow us in the future to have an alternative implementation for recovery
without these flaws. I.e. notifications go to a separate lean Kafka topic
which is read by all client nodes. On recovery:
- a mark is written
- wait until mark offset confirmed replicated in the notification topic
  (with potential fallback to polling of the pointer table in Cassandra)
- recover from Cassandra only

Pull Request Pull Request #720: Add ReplicatedOffsetNotifier callback

Run Details

3177 of 3816 relevant lines covered (83.25%)

1.41 hits per line

evolution-gaming / kafka-journal / 13200507137 / 1
83%
master: 94%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job Scala 2.13.16 - 13200507137.1

evolution-gaming / kafka-journal / 13200507137 / 1 83% master: 94%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job Scala 2.13.16 - 13200507137.1

evolution-gaming / kafka-journal / 13200507137 / 1
83%
master: 94%

README BADGES
x