Re: [akka-user] Having Sharded Persistent Actors reset persistence data on initialization

You must know the entity identifiers, so they must register themselves somewhere. If those are using Akka Persistence you could use Persistence Query to retrieve all persistence ids, which can probably be correlated to entity ids. That is not something you would like to do for each broadcasted

Re: [akka-user] Having Sharded Persistent Actors reset persistence data on initialization

>> Exactly, so you would have to have another actor (at least one) on each node that is always alive and subscribes to pubsub and delegates to the ShardRegion. So no straightforward way to broadcast to all instances of an aggregate? On Thu, Mar 9, 2017 at 10:52 PM, Patrik Nordwall

Re: [akka-user] Having Sharded Persistent Actors reset persistence data on initialization

On Thu, Mar 9, 2017 at 7:42 PM, Richard Ney wrote: > In a sharded system the life-cycle of the actor is controlled by the Shard > actor. So if you are subscribing to distributed pub/sub in your actor's > constructor or receive method and you passivate there is no way for

Re: [akka-user] Having Sharded Persistent Actors reset persistence data on initialization

In a sharded system the life-cycle of the actor is controlled by the Shard actor. So if you are subscribing to distributed pub/sub in your actor's constructor or receive method and you passivate there is no way for the Shard actor to respawn your passivated actor because the message isn't coming

Re: [akka-user] Having Sharded Persistent Actors reset persistence data on initialization

Is it true that - Passivated (sleeping) actors aren't able to listen to the pub/sub topic. ? Unfortunately there's no answer here: http://stackoverflow.com/questions/40782570/can-akka-distributedpubsub-deal-with-passivated-subscribers On Wed, Mar 8, 2017 at 6:18 PM, Richard Ney

[akka-user] Having Sharded Persistent Actors reset persistence data on initialization

Environment: - Distributed cluster with persistence sharded actors. - Persistent actors are setup to Passivate when inactive. - All actors have the Backoff Supervisor wrapping the actual persistent actor - Shard regions are common across our users Problem: - At times