Yep, start the router on the "chunk" node. Pay attention to the path in the configuration file, it must match the semi-absolute (without /user) path of your router actor.
Then also remove the unnecessary and confusing routees.paths from the config. Heiko On Thu, May 15, 2014 at 6:03 PM, Eugene Dzhurinsky <[email protected]>wrote: > On Thu, May 15, 2014 at 05:58:32PM +0200, Heiko Seeberger wrote: > > Taking a closer look at your configuration, I see that you are using a > pool > > router, but also configure routees.paths. That won't work as expected: > Pool > > routers create routees as child actors and group routers use given > routees. > > Please find the details in the router documentation, then decide what you > > want to achieve. > > Actually I *want* to start routees on remote nodes, so this is desired. I > assume that this should work: > > - create an empty actorsystem with cluster and remoting support on a "http" > node" > - configure a pool router on "chunk" node > - upon sending a message to the router, it will perform some lookups and > create it's routees on the remote node > > So the only thing I didn't do - is that I didn't start the router actor. > > Am I missing something? > > -- > Eugene N Dzhurinsky > -- Heiko Seeberger Twitter: @hseeberger Blog: blog.heikoseeberger.name -- >>>>>>>>>> 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.
