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
The RecoverySuccess message sent back to the CurrentEventsByTagPublisher contains the wrong sequence number. Right now we are sending back the highest sequence number found in the first limit messages, where limit defaults to 500. This is wrong - we should query to see _what the highest sequence number is for this query at the time it began.
So we need to change the MongoDbJournal itself to support this, and it's possible that the underlying EventsByTagPublisher implementations have bugs in their guts too.
Ran into this while replaying a large data set last week - going to work on a reproducer + fix for it.
The text was updated successfully, but these errors were encountered: