Scala version : 2.11.7
Akka version : 2.4.17
-
Hi Akka Team,
I'm writing an Akka application using Akka Cluster, Akka Actors and Akka
Stream. I have a cluster of 3 nodes : 2 workers and 1 node consuming data
from a source.
I want three configs files : application.conf, node.worker.conf
This is now how a fork-join pool works basically.
Please read the docs about managing blocking:
https://doc.akka.io/docs/akka/2.5/scala/dispatchers.html#blocking-needs-careful-management
Tuning the default dispatcher like you’re attempting to here would not have
a positive effect by the way.
Plea
I am doing akka cluster client program to send messages to another cluster
but i can't find any relevant code as i beginner to akka can anyone send me
relevant akka cluster client code with simple displaying message to another
cluster
Thanks & Regards ,
V Sai Kiran Sarma
--
>>
Hi,
I know that I needs to be careful when I have blocking tasks but in the
context of my app, I have no blocking tasks (or blocking calls).
To give more details, my two nodes workers has a router (round robind
group) with 10 workers actors each. All my workers are stateless and
execute most
Hi,
Did you read that the following post
: http://developer.lightbend.com/guides/akka-sample-cluster-scala/ ?
Le jeudi 28 septembre 2017 11:20:22 UTC+2, Kiran Sarma a écrit :
>
> I am doing akka cluster client program to send messages to another cluster
> but i can't find any relevant code as
Hi Kilic,
Try looking at stack traces during the busy periods (e.g. use `jstack` on
the command line to gather some), that should give you a clue what's going
on. In the picture you sent in your first email there were actually only 8
regular pool threads. Are there times where more is going on
Hi Unmesh,
On Wednesday, September 27, 2017 at 3:01:24 PM UTC+2, Unmesh Joshi wrote:
>
> I was trying to go through the code to understand how GraphStages receive
> actor messages. I see that GraphStageActor is a actor not created like
> normal actors. I looks like all the messages to GraphStage
Hi,
I will run the code in local and make thread/stack dump.
I attached all the living threads of my worker.
Le jeudi 28 septembre 2017 12:18:56 UTC+2, johannes...@lightbend.com a
écrit :
>
>
> Hi Kilic,
>
> Try looking at stack traces during the busy periods (e.g. use `jstack` on
> the c
Hi Simon,
as Johan said, you shouldn't use `get` to wait for the result of future.
This just synchronously blocks the thread from doing any other useful work.
Instead, you can asynchronously handle the result of the future once it is
available. Because it is so common, we have a pattern for thi
Yeah. I meant ActorRef for GraphStage. My only question then is, if
messages to all the GraphStage Actors get serialized to
ActorGraphInterpreter, will that potentially limit the possible parallel
execution? e.g. If HttpRequestParserStage and HttpResponseRendererStage
both receive actor messag
Correct, it will limit parallelism. I usually see the streams
infrastructure more as a control channel that makes sure that data flows
correctly. These kind of control things shouldn't require much overall CPU
share so it should not matter so much. If you want to do CPU-intensive work
you need
Thanks, this makes it clear.
Btw, one thing I am trying to understand is, when will be the stream not
'fused'? When 'async' boundaries are inserted?
On a separate note, I am trying to create a very thin slice through Akka
HTTP, Akka Streams, Akka IO and Java NIO. A very simple Http server which
Hi Johannes,
Thank you for looking into that.
This is really surprising finding. I cannot find anything wrong with my
code though in this regards. There is one more materializer beining
initialized, but for an endpoint that is rarely used (Swagger docs - I have
verified in the logs, that there ar
This is explained in this blog post:
https://akka.io/blog/2016/07/06/threading-and-concurrency-in-akka-streams-explained
and the docs:
https://doc.akka.io/docs/akka/current/scala/stream/stream-parallelism.html#pipelining-and-parallelism
Thanks for sharing your repo, I think it’s a bit weird to gu
Thanks for the links.
The repo is not really for beginners, but for people who want to understand
akka http source code. I thought instead of going through all the akka-http
and akka repo, if its possible to carve out a minimal subset, it will be
lot easier for developers. It was of use to our tea
15 matches
Mail list logo
