Hi again,
I tweaked one of the samples and I can reproduce this strange behaviour.
Please create a ticket, and I will investigate it further.
http://doc.akka.io/docs/akka/current/project/issue-tracking.html
Regards,
Patrik
On Wed, Jan 29, 2014 at 2:10 PM, Patrik Nordwall
wrote:
> The configura
The configuration looks correct. I can't see what could be wrong at the
moment.
Are you sure that the cluster is stable (no membership changes) when you do
the testing?
You should upgrade to 2.3.0-RC1, but I don't think we have changed anything
related to this.
/Patrik
On Wed, Jan 29, 2014 at 1
Hi,
that is exactly what I tried. I checked my configs, tried again and it
din't work.
I am using every akka package in version 2.3-M2 btw.
The config for my public-nodes (a second with port changed to 2252)
akka {
extentions = ["akka.contrib.pattern.ClusterReceptionistExtension"]
actor
Hi,
What you are looking for is possible with a consistent-hashing-group
combined with cluster node roles.
In the config of the routee-nodes you define
akka.cluster.roles=["routee-node"].
In the router config of the public-nodes you define use-role="routee-node".
In the config of the public-nodes
I know, that if I use a consistent hashing group router, it will always
rout to the same registered routees.
So I wrote my application, with a few routees on there own routee-nodes and
a public-node with a router, which is reachable by the client.
If the client sends a message it is routed
