It is expected that it detects crashed/stopped nodes as unreachable. When
unreachable have been downed and removed the cluster canmove joining nodes
to Up. I'm not sure I understand the question/problem.
Also, don't change heartbeat-interval. That will not make anything better.
acceptable-heartbea
Are you specifically talking about Distributed Pub-Sub?
Can you please elaborate on this?
If I were to just use AKKA for point-to-point communication between multi
sites, would there be any problem there?
On Wednesday, September 7, 2016 at 2:34:09 PM UTC+3, Guido Medina wrote:
>
> Short answer i
Hi,
I am trying to define custom logic for the shape with several inlets (for
example custom shape with 2 or more inlets).
I was trying to avoid defining out handler for the Outlet, however it
throws an error, so I suppose that there is no default behaviour in the
shape class.
The problem is
You use noSender in ActorA when sending START. Use self instead.
/Patrik
tors 29 sep. 2016 kl. 19:20 skrev :
> On Wednesday, September 28, 2016 at 1:55:42 PM UTC-7, que...@gmail.com
> wrote:
>>
>> I have one actor that sends a message to another actor. There is a
>> message logged that the message
You find most of the answers here:
http://doc.akka.io/docs/akka/2.4/intro/deployment-scenarios.html
It will be removed in Akka 2.5, unkown release date.
/Patrik
tors 29 sep. 2016 kl. 22:18 skrev Joseph Mansigian <
joseph.c.mansig...@gmail.com>:
>
> I read that the Microkernal was going away. Wo
On Linux you can use taskset to pin the jmv process to specific cores.
fre 30 sep. 2016 kl. 19:56 skrev Konrad Malawski <
konrad.malaw...@lightbend.com>:
> That's what containers are for though.
> Run your jvm in a container and restrict resources available to that one
>
> On 30 Sep 2016 19:48, "R