Skip to content
This repository has been archived by the owner on Jun 1, 2021. It is now read-only.

Replay from Cassandra stops prematurely if there are large sequence number gaps covering empty partitions #403

Open
volkerstampa opened this issue Feb 1, 2018 · 1 comment
Assignees

Comments

@volkerstampa
Copy link
Contributor

After disaster recovery the local sequence is potentially adjusted to ensure that it is larger than the local log's time (see also commit for #286). If Cassandra is used as backend and the gap introduced through this adjustment covers empty partitions, replays from this event log stop prematurely as they do to proceed after the first empty partition.

@volkerstampa volkerstampa added this to the 0.11 milestone Feb 1, 2018
@volkerstampa volkerstampa self-assigned this Feb 1, 2018
volkerstampa added a commit that referenced this issue Feb 1, 2018
Do not stop reading events from EventLog on empty partitions if
the toSequenceNr is known (i.e. not Long.MaxValue)

Closes #403
volkerstampa added a commit that referenced this issue Aug 14, 2018
Do not stop reading events from EventLog on empty partitions if
the toSequenceNr is known (i.e. not Long.MaxValue)

Closes #403
@volkerstampa
Copy link
Contributor Author

This fix had to be reverted with #407

@volkerstampa volkerstampa reopened this Aug 15, 2018
@volkerstampa volkerstampa removed this from the 0.11 milestone Aug 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant