Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Recovery can return items out of order #131

Open
Aaronontheweb opened this issue Feb 1, 2022 · 0 comments · May be fixed by #132
Open

Recovery can return items out of order #131

Aaronontheweb opened this issue Feb 1, 2022 · 0 comments · May be fixed by #132
Assignees
@Arkatufus
Labels
bug

Comments

@Aaronontheweb
Copy link
Member

Aaronontheweb commented Feb 1, 2022 •
edited
Loading

Version Information
Version of Akka.NET? v1.4.32
Which Akka.NET Modules?

Describe the bug
Have seen incidences inside Phobos traces that indicate that the journal is delivering its RecoverySuccess message prior to returning the final ReplayedMessage from inside the journal, resulting in an invalid recovery.

To Reproduce

  1. Create a ReceivePersistentActor that recovers an event type that is not handled as a Command<T>
  2. Persist 100 of this event type
  3. Test to see if an Unhandled version of this event type appears, sent immediately after RecoverySuccess

Expected behavior
RecoverySuccess is the final message sent to the persistent actor after recovering from PostgreSql.

Actual behavior
RecoverySuccess can be sent to the persistent actor prior to one of the events its recovering.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Arkatufus Arkatufus

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: Recovery messages can arrive out of order Arkatufus/Akka.Persistence.PostgreSql
2 participants
@Aaronontheweb @Arkatufus