You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.
today we paid attention on the snapshot topic. I was wondering why Eventuate considers the lastHandled event for the snapshot write/read process.
Let's assume the following case:
We have actor A and B and two events E1 and E2.
Actor A consumes E1 and actor B consumes E2.
Let's say we have just few E1's and millions of E2.
When writing a snapshot actor A takes the lastSequenceNo of the latest consumed E1, ignoring the maybe millions of E2 afterwards.
On the next actor recovery, it takes much longer as it needs to.
My question: Wouldn't it be better to take the sequenceNo of the "lastReceived" event instead? Actor A then can start with replication progress with a much higher sequenceNo.
The text was updated successfully, but these errors were encountered:
Hi @krasserm,
today we paid attention on the snapshot topic. I was wondering why Eventuate considers the lastHandled event for the snapshot write/read process.
Let's assume the following case:
On the next actor recovery, it takes much longer as it needs to.
My question: Wouldn't it be better to take the sequenceNo of the "lastReceived" event instead? Actor A then can start with replication progress with a much higher sequenceNo.
The text was updated successfully, but these errors were encountered: