[akka-user] Akka cluster sharding topology aware

Akka sharding creates actors lazyly, if one message is directed to an non initialized actor, the Akka sharding module will create a new instance. I didn't understand your question. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] OutOfMemoryError due to too much logging

Hi, I sometimes see this issue where I want to switch logs to DEBUG, but due to the large number of messages the JVM will crash on OutOfMemory which turns out to be due to the accumulation of logging events. Most logging frameworks have the ability to drop messages beyond a certain number and

[akka-user] Re: Back pressure not working...

These are good tips and to be honest I've considered them. But it doesn't really answer my question -- why is back pressure not working in my example? Do I need additional configuration? Limit buffer size? On Saturday, December 12, 2015 at 7:17:20 PM UTC-5, matheus...@gmail.com wrote: > >

[akka-user] Re: access to HttpRequest rendering layer to help support "batched" requests

The recommendation from https://github.com/akka/akka/issues/19062 is to use a http Bidi to handle the rendering in a nice non-api exposing way. The idea is to get a ByteString that is the result of the http layer rendering a HttpRequest. You can do something like this to get a bidi flow: val

[akka-user] Akka cluster sharding topology aware

Hi, I have been using cluster sharding feature in akka 2.4.1. I would like the sharding to be topology aware. For example : if I have a cluster with nodes - n1,n2,n3,n4. If my request goes to node n1 and if the entity actor does not exist in the cluster then it must create the entity actor

Re: [akka-user] Akka cluster sharding topology aware

Allocation happens at the shard level, i.e. for groups of actors, see `ShardCoordinator.ShardAllocationStrategy`. Therefore I don’t think you can achieve what you described. Heiko -- Heiko Seeberger Home: heikoseeberger.de Twitter: @hseeberger