These are chat archives for akkadotnet/akka.net
I was wondering if someone could help me with clustering. As I've clearly missed something.
I'm playing with the samples (Cluster Transformation), and I'm trying to work out how to ensure there is on a single version of an actor with the same ID in the cluster.
In the sample, the LaunchBackend function is creating an actor with the path "backend". My initial understanding was that the paths would be unique over the cluster?
What's the pattern / example for ensuring an actors path is unique within the cluster? Is this a configuration change? Do I need to use cluster routers? (I've been trying this but there doesn't appear to be any change in behavior).
All help is much appreciated.
@pablocastilla Thank you!
So I tried a router with this config (adjusted for the example), but it still allowed duplicates.
router = consistent-hashing-group
routees.paths = ["/user/backend"]
enabled = on
nr-of-instances = 1
allow-local-routees = on
use-role = server
RE: creating an actor and direct access, do you mean creating an actor which subscribes to the cluster state and then having it handle direct assignment / reassignment via remote deploys. (I can do this, I just thought clustering gave me this out of the box)
@pablocastilla As in try to get the routing to work? Fair enough, that seems like far less work. I really appreciate the remoting suggestions tho!
Any of the seasoned clustering pro's have some thoughts on how to get routing to do this?
@rogeralsing Thank you! That's great news - if I check out the cluster sharding branch would I get a functional preview or is a little while off.
@bobanco Thank you for clearing that up - I 100% understand now :)
@rogeralsing Thank you - I'll check it out!
Very excited for this next release!