GitHub user raboof added a comment to the discussion: Race Condition in Persistent FSM Actors During Deployment with Multiple Instances
It is indeed the case that Pekko Persistence works on the 'single writer' principle, so having new and old versions of the same persistence ID writing at the same time is not allowed. The solution here is indeed to introduce Pekko Cluster and use Cluster Sharding to manage the persistent entities: Cluster Sharding can make sure persistent entities are gracefully migrated to the new nodes during a deployment. GitHub link: https://github.com/apache/pekko/discussions/1573#discussioncomment-11732169 ---- This is an automatically sent email for notifications@pekko.apache.org. To unsubscribe, please send an email to: notifications-unsubscr...@pekko.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: notifications-unsubscr...@pekko.apache.org For additional commands, e-mail: notifications-h...@pekko.apache.org
