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
Since Akka.Persistrence.PostgreSql does its own thing with serialization, the writerUUID column was never added to it. Thus we don't have an easy way of debugging scenarios where multiple nodes are all attempting to write to the same entity. I have this exact problem with a user right now where it appears as though multiple separate users are competing for the same journal entries for the same entity.
To fix this, we're going to need to either:
Update the DDL and table schema - adding a new field.
Change the serialization system for Akka.Persistence.PostgreSql to include this data and avoid a schema migration.
cc @to11mtm should we just ditch this and go with Linq2Db? I'm starting to get that impression.
The text was updated successfully, but these errors were encountered:
Version Information
Version of Akka.NET? 1.4.35
Which Akka.NET Modules? Akka.Persistence.PostgreSql
Describe the bug
Related: akkadotnet/akka.net#3811
Since Akka.Persistrence.PostgreSql does its own thing with serialization, the
writerUUID
column was never added to it. Thus we don't have an easy way of debugging scenarios where multiple nodes are all attempting to write to the same entity. I have this exact problem with a user right now where it appears as though multiple separate users are competing for the same journal entries for the same entity.To fix this, we're going to need to either:
cc @to11mtm should we just ditch this and go with Linq2Db? I'm starting to get that impression.
The text was updated successfully, but these errors were encountered: