-
Notifications
You must be signed in to change notification settings - Fork 784
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.
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
Aggregate snapshotter stops working #2770
Comments
CauseI think this happens because you have a massive aggregate, @unisteven. The fact it's big very likely means it handles numerous commands, potentially at the same time. This wouldn't impact snapshot creation necessarily, as they should be unique based on the sequence. How this idea correlates with "...once our database gets filled with loads of events (100K+) it will stop working entirely..." isn't clear to me though. SolutionAs I am working on hunches here, I'd be hard-pressed to give a solution. One thought that crosses my mind is introducing a form of snapshot warm-up service (as described in this issue). Other pointersI do have a couple of other recommendations concerning the scenario you describe:
Issue managementI am not overly certain this is a bug in Axon Framework. |
Basic information
Steps to reproduce
I cannot share our codebase since it is closed source, but here's the scenario:
We have a microservices setup with Spring Boot on the Axon Framework. We have been running this in production for about a year and we have seen this setup working throughout that period.
In our code base there is a big aggregate that handles a lot of events (100K+) and this takes a while to event-source, to speed this up we added the default aggregate snapshotter
Expected behaviour
We would expect that the aggregate snapshotter would create a snapshot and use this to build up the aggregate from the last state it was in when the snapshot was taken (every 10 events in our case)
Actual behaviour
This works fine for a while, but once our database gets filled with loads of events (100K+) it will stop working entirely and throw the following error:
What we have tried
Once we reset the entire database it will start working again (for a while)
What could be causing such an error, and what would be a possible solution?
The text was updated successfully, but these errors were encountered: