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
Hello. I have a project that for testing uses the akka-persistence-inmemory. The problem is that the snapshot sequence number is not increased. I cannot publish the code since is private but I just create a simple PersistentActor and call the saveSnapshot(...) 3 times. I have another actor recovering with the same persistence ID and it gets the latest snapshot but the sequence number is 0 and it should be 3. I checked the log and I do get 3 SaveSnapshotSuccess(---) messages but they all have the same sequence number. Anyone know why?
The text was updated successfully, but these errors were encountered:
Hello Dennis,
About this issue. I do not think it is a bug. It is not well documented.
The persistence number is increased as soon as you persist in something
before. So, if you snapshot without having persisted you end up having
snapshot a seqnr 0. If you do another snapshot then again that snapshot is
at 0. Only persistence increases the number. If this is the intended
behaviour then everything is fine and you can close the bug report but
maybe add the documentation. If not, I plan to add a pull request to Akka
itself and explain the behaviour in detail since I feel more than one will
have trouble getting their head around this persistence seqnr.
Best regards,
Vlad Filip
Hello. I have a project that for testing uses the akka-persistence-inmemory. The problem is that the snapshot sequence number is not increased. I cannot publish the code since is private but I just create a simple PersistentActor and call the saveSnapshot(...) 3 times. I have another actor recovering with the same persistence ID and it gets the latest snapshot but the sequence number is 0 and it should be 3. I checked the log and I do get 3 SaveSnapshotSuccess(---) messages but they all have the same sequence number. Anyone know why?
The text was updated successfully, but these errors were encountered: