Hi,

I'm trying to implement persistence of entries (as in their presence not
their data) in a ClusterSharding based system. For the moment I have a
persistent ClusterSingleton that creates all entries, so that in the
event of a full cluster restart every running entries would be
re-created (by sending them an Init message).

The only issue is that (before ClusterSharding) this singleton was
watching the created child so that it knew when those would disappear
(and thus know processing is over for this entry).

In the ClusterSharding, is there a way to do that, beside sending the
Passivate also to my singleton?

Next, I've noticed that Akka master ClusterSharding seems to implement
what I did with the "rememberEntries" parameter, in certainly a
clever/better way than my poor-man's implementation. Is this new contrib
compatible with the latest Akka 2.3? 
How to use this newer version?

And finally, is there a way to roughly get access to the list of running
entries (their ids for instance) in a given cluster? Or at least to ask
the local Region for the entries running on a given node?
This is so that I can provide this information to a management layer we
have on our system.

Thanks!
-- 
Brice Figureau
My Blog: http://www.masterzen.fr/

-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to