Hi guys,
I have a sharding region that creates instances of ActorA
I want to "ask" (in order to get a synchronous reponse) the region to do
something
The problem is ActorA (that will receive the message) will dispatch the
work to ActorB and ActorC and will expect messages from them.
When
I solved my issue with changing the roles names !
Le jeudi 30 mars 2017 18:01:51 UTC+2, Kilic Ali-Firat a écrit :
>
> Hi Akka Team,
>
> Using the akka cluster samples, I defined a cluster router (group) and I
> want to validate my cluster using unit test.
>
> The problem is that the master
Hi Jozsef, when cross-posting at least take the effort to copy the
message...
Just posting more links via more channels seems very "nagging".
If you want ASAP answers we offer commercial support, otherwise please be
nice and patient when asking the community for help.
Thanks for your
Thanks for the info.
I don't really know what is the connection between Akka and Lightbend.
I was thinking this is a community Akka channel and not a commercial
channel for advertising Lightbend, or is it ?
On Fri, Mar 31, 2017 at 12:40 PM, Konrad Malawski <
konrad.malaw...@lightbend.com>
Originally I decided not to copy here the question because that is more DRY
but if it is considered nicer to copy the SOF question, of course can do
that, no problem.
The question from SOF :
If I set a breakpoint here
Sure, it is the community - so please be nice to it :-)
It is not nice to go over all possible channels just sending links to stack
overflow.
At least re state your question or that you did not get an answer there etc.
Asking for help works better if you're nice about it.
--
Konrad `ktoso`
Thanks for sharing. Interesting that it would make such big difference.
If you ever need better remoting performance you should try the new
implementation, called Artery.
It should not be a big difference for these message rates, though.
Actors are objects that are scheduled on Kernel threads using ForkJoin Pool?
That's how they're implemented yeah - tasks submitted to a pool.
But that misses all the things which make the model useful: isolation and
location transparency (the most important one!).
So you don't care if an actor
Got it! Thanks a lot!
On Friday, March 31, 2017 at 3:56:08 AM UTC-7, Konrad Malawski wrote:
>
>
> Actors are objects that are scheduled on Kernel threads using ForkJoin
> Pool?
>
> That's how they're implemented yeah - tasks submitted to a pool.
>
> But that misses all the things which make the
Hi All,
I wonder what is an Actor underneath ? I mean I understand that they are
Object that have a state, mailbox , listeners and all that but the moment I
hear Actors can "crash" and "restart and run or process again" I think of
it as some scheduling/processing entity and I wonder if that
We finally figured out this issue.
We had to optimize the send-buffer-size and receive-buffer-size on both
client and server to be able to increase the number of concurrent requests.
This settings is on remote.netty.tcp.
Measuring the time delay between sending and receiving the message
I have an actor that I would like to not fail. However there is a
possibility that a user might call the actor with some problem that results
in an exception not being thrown. The proscribed way to handle this is to
fial the actor and have the supervisor restart the actor, however that is
not
Do you know the forward() function on ActorRef? I'm not certain whether
it's right for your use case, but it's often the answer to this sort of
design, since it sends a message while preserving the original sender. If
ActorA doesn't actually need the response, it's probably correct. (The
reason
I was looking at the implementation of the reactive-kafka ProducerStage.
Very interesting.
https://github.com/akka/reactive-kafka/blob/master/core/src/main/scala/akka/kafka/internal/ProducerStage.scala
It seems this pattern could be used for any external API that returns a
Future.
By contrast,
Hi Akka Team,
It's again me about the multi-nodes test that I'm doing to validate my
cluster. I solve my issues about Master-Worker communication but I have a
really weird behavior in my test. The below piece of code seems to be
execute 3 three times :
awaitAssert {
/**
15 matches
Mail list logo
