java - Akka clustering - one Manager Actor per node -
i’m working on application queries large number of actors , hence sends / receives large number of messages. when application ran on single machine not issue because messages sent within boundaries of single jvm quite fast. however, when run application on multiple nodes (using akka-cluster) each node hosts part of these actors , messages go on network becomes extremely slow.
one solution came have manageractor on each node application ran. minimize number of messages exchanged (i.e. instead of sending thousands of messages each of actors, if run application on 3 nodes send 3 messages - 1 each manageractor sends messages within current jvm other (thousands of) actors fast). however, i’m new akka , i’m not quite sure such solution makes sense. see drawbacks of it? other options better / more native akka?
you use akka's distributed publish-subscribe achieve that. way start manager actor on each node usual way, have them subscribe topic, , publish messages them using topic topic. there simple example of in docs linked above.
Comments
Post a Comment