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
Let's say orderservice crashed and lost all the data (not in this example, since order and customer share same db here), how can we replay all the events and restore its latest state?
In io.eventuate.local.db.log.common.DbLogBasedCdcProcessor,
The offsetStore always seeks to the latest offset even though its consumer starts at the earliest.
I guess we can either make it configurable or provide a different implementation of the CdcProcessor.
But the question is, while we replay all the events, the orderservice will emit new events as well, and those events are already published and stored in the event store. So, what do we do? publish them to a separated Topic? What's the recommended operation? Or, is it really practical?
The text was updated successfully, but these errors were encountered:
Let's say
orderservice
crashed and lost all the data (not in this example, since order and customer share same db here), how can we replay all the events and restore its latest state?In
io.eventuate.local.db.log.common.DbLogBasedCdcProcessor
,The
offsetStore
always seeks to the latest offset even though its consumer starts at theearliest
.I guess we can either make it configurable or provide a different implementation of the
CdcProcessor
.But the question is, while we replay all the events, the
orderservice
will emit new events as well, and those events are already published and stored in the event store. So, what do we do? publish them to a separated Topic? What's the recommended operation? Or, is it really practical?The text was updated successfully, but these errors were encountered: