I was looking to know how to write an actor per request. I want to
understand this pattern so I could create a sample similar to the one at
https://github.com/muuki88/activator-play-cluster-sample that creates a
frontend for an akka cluster in Java.
I'm struggling with how to have a frontend
Hi Vitaliy,
Do you send large messages or send messages without backpressure? Since
2.2.x does not prioritize internal heartbeat messages over user messages it
can accumulate delay. You should try throttling or backpressuring your
remote sends first to see if it is the problem.
-Endre
On Mon,
Hi John,
I was looking to know how to write an actor per request. I want to
understand this pattern so I could create a sample similar to the one at
https://github.com/muuki88/activator-play-cluster-sample that creates a
frontend for an akka cluster in Java.
I'm struggling with how to have a
Hi Leon,
I've been looking at the new expermental http server and the tcp echo
server / client. and it looks really promising!
Is it possible to create a http client using the current api (0.4), and if
so, how can I adapt the tcp client code to do a http request instead?
It is possible
Hi Eugene
The order of the seed nodes in the list is important, since the first one
is important in the bootstrapping process:
http://doc.akka.io/docs/akka/2.3.4/scala/cluster-usage.html#Joining_to_Seed_Nodes
[...] the node configured as the first element in the seed-nodes
configuration list
Thanks. I will just have to wait for the official client :)
--
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
On Tue, Jul 22, 2014 at 10:45:41AM +0200, Akka Team wrote:
Hi Eugene
So you should have the same node as the first one in the seed node list on
both machines.
Okay, that's clear. So in some case I need to have some dummy cluster node
acting as a seed node and deployed onto a component of the
On Tue, Jul 22, 2014 at 4:25 PM, Eugene Dzhurinsky jdeve...@gmail.com
wrote:
On Tue, Jul 22, 2014 at 10:45:41AM +0200, Akka Team wrote:
Hi Eugene
So you should have the same node as the first one in the seed node list
on
both machines.
Okay, that's clear. So in some case I need to
I recently posted this question on Stack Overflow, as Waiting on multiple
Akka FSM messages
https://stackoverflow.com/questions/24872342/waiting-on-multiple-akka-fsm-messages.
I got one great answer (reproduced below) from Konrad 'ktoso' Malawski. I'm
reposting it on this list just in case
Thanks for the detailed reply on SO! We're almost certainly going with your
recommended method of tagging requests and responses with an id field, but
I thought a wider discussion could be interesting.
On Tuesday, July 22, 2014 10:59:41 AM UTC-4, Konrad Malawski wrote:
You're welcome :-)
I run cluster of Actor nodes on AWS Autoscaling groups.
Before migration to version 2.3.4, cluster discovery worked just fine: new
instances join cluster, terminated machines switched to Unreachable and
Down state.
After switching to 2.3.4, I see that terminated instances never leave a
This is an issue I've been dealing with for a while now. I was hoping that
the fix for log-remote-lifecycle-events = off in 2.2.4 would've fixed it
but it hasn't.
During multi-JVM cluster testing, we remove and re-add a node to test
failure handling:
Hi.
First of all thanks for your time on this.
I'm using Akka version 2.3.4 (Java).
I've stopped an actor
getContext().stop(getSelf());
and when I look at the rebalance() method in my AllocationStrategy I still
see the entry in the sharding region corresponding to the stopped actor.
Konrad, thanks for the reply and input. I agree that I should just test it
out and see what / if anything gets clogged and use introspection tools to
find out what is going on.
Cheers,
Greg
On Monday, July 21, 2014 2:33:08 AM UTC-7, Konrad Malawski wrote:
Hi guys,
That's an interesting
14 matches
Mail list logo
