I have a routed Akka actor whose routees spawn child actors of another type. I have no need for the spawned children to be associated with a specific routee and am actually finding this to be a disadvantage. I'd expect to be able to address these children by the path /RoutedActor/ChildActorName but I'm finding them under a path that includes the routee's name: /RoutedActor/$a/ChildActorName. I have no idea which routee spawned a given child, so I've worked around this by wildcarding the path for my ActorSelections (/RoutedActor/*/ChildActorName).
This has got to be a pretty inefficient way to find an actor.
I understand that these children are actually grandchildren of the router, but this is really a big drawback in the router pattern. Just by adding routing to parallelize some work, I broke my ActorSelections and now don't know the actual path to any of my child actors. Is there a way to make the child actors direct children of the router, and if so, are there any disadvantages to this? I'm not finding anything on this in the Akka documentation (v2.3.7).