Re: [akka-user] Re: Cluster actors an parallelism

2016-08-26 Thread Patrik Nordwall
You could have only one routee per node that creates child actors and delegates the actual work to them. Another flexible and dynamic approach is to use Distributed Pub Sub as a "router": http://doc.akka.io/docs/akka/2.4/scala/distributed-pub-sub.html On Thu, Aug 25, 2016 at 11:20 PM, Cosmin Margi

Re: [akka-user] Subscribing to PersistentShardCoordinator startup failure

2016-08-26 Thread Patrik Nordwall
There is no such feature. You can ping a dummy entity and see if you get a reply. If it repeatedly times out you are in trouble. However, I think you should solve the root cause of the problem. The typical mistake is to use auto-down and thereby get split clusters as described in the documentation

Re: [akka-user] Subscribing to PersistentShardCoordinator startup failure

2016-08-26 Thread Justin du coeur
Time for another radical suggestion: I really think y'all should just excise auto-down from the documentation, and probably drop the feature entirely. It doesn't add an awful lot of benefit (since people who are getting started usually aren't dealing with downing), and it's *way* too easy to get y

Re: [akka-user] Subscribing to PersistentShardCoordinator startup failure

2016-08-26 Thread Patrik Nordwall
It's a fair point. I would like to have a good alternative, built-in. I'll see what I can do. On Fri, Aug 26, 2016 at 2:24 PM, Justin du coeur wrote: > Time for another radical suggestion: I really think y'all should just > excise auto-down from the documentation, and probably drop the feature >

Re: [akka-user] Delay within GraphStageLogic

2016-08-26 Thread Gary Struthers
Thanks Konrad, but I posted because I tried scheduleOnce and got no delay scheduleOnce(logger.debug("1 currentTimeMillis {}", System.currentTimeMillis()), FiniteDuration(100, MICROSECONDS)) scheduleOnce(logger.debug("2 currentTimeMillis {}", System.currentTimeMillis()), FiniteDuration(100, MI

Re: [akka-user] Delay within GraphStageLogic

2016-08-26 Thread Endre Varga
Hi Gary, On Fri, Aug 26, 2016 at 6:17 PM, Gary Struthers wrote: > Thanks Konrad, but I posted because I tried scheduleOnce and got no delay > > scheduleOnce(logger.debug("1 currentTimeMillis {}", System. > currentTimeMillis()), FiniteDuration(100, MICROSECONDS)) > > scheduleOnce(logger.debug("2

[akka-user] akka-kafka-stream "Offset Storage in Kafka" question/clarification

2016-08-26 Thread Drew Kutcharian
Hi, In the "Offset Storage in Kafka” on http://doc.akka.io/docs/akka-stream-kafka/current/consumer.html#offset-storage-in-kafka there is the following example: .groupedWithin(10, 5.seconds) .map(group =>

Re: [akka-user] Delay within GraphStageLogic

2016-08-26 Thread Gary Struthers
Sorry, my onTimer() doesn't fire. It looks like all I need to do is 1. use TimerGraphStageLogic 2. call scheduleOnce 3. override onTimer. I am misusing Resume for retries but I've tried scheduleOnce in other places and it still doesn't fire. Here's an example, override def createLogic(inheri

Re: [akka-user] akka-kafka-stream "Offset Storage in Kafka" question/clarification

2016-08-26 Thread Patrik Nordwall
The commit commands are emitted to the underlying KafkaConsumer in right order. It is waiting for the results of the commits that are done in parallel, and will possibly increase total throughput. We observed better throughput in performance tests. It would be great to clarify this in docs. You ar