-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Closed
Labels
1 - triagedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedhelp wantedIssues that the core team will likely not have time to work onIssues that the core team will likely not have time to work ont:persistence
Milestone
Description
Currently errors in persistenceId naming lead to nasty internal clashes which get reported through error messages like
Invalid replayed event [1] in buffer from old writer
Since this is an api user error rather than a core akka error, the error should be more obvious or helpful, suggest inclusion of text "possible persistenceId name duplication" in the error text.
Also maybe some paragraph on trouble-shooting in the akka docs. One problem is this error can manifest in different ways but at the time of creating two persistors with conflicting ids you get no warning.
A better solution would be to detect the problem when the it first arises - i.e. first time two active persistors use the same id - but I've no idea whether this is practical
Metadata
Metadata
Assignees
Labels
1 - triagedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedTickets that are safe to pick up for contributing in terms of likeliness of being acceptedhelp wantedIssues that the core team will likely not have time to work onIssues that the core team will likely not have time to work ont:persistence