We noticed that there could be the situation that the SNAPSHOT_EVENT_ENTRY table could have no
snapshot entries for a specific aggregate in concurrency situations.
We are using DB2 as a database and an Isolation-Level of READ_COMMITTED.
Although the deletion and recreation of SNAPSHOTS is done in one transaction, it seems
to us that another axon instance could see no snapshot at all for a specific aggregate.
That seems to have the effect that an aggregate has to be created by processing all events which
could consume a lot of time and memory.
Has anyone else recognized this effect? We already tried to rise the db isolation level with no success…