Thanks Patrik. I get your point. I have changed my code to lookup actor
using ActorSelection rather than passing around ActorRef. It is working
smooth. After rethinking I have decided to just use one ActorSystem as
there is no explicit need for the second ActorSystem.
Thanks,
Prashanth
On
Hi Klaus, I am also interested in this subject and posted something before
deleting it after seeing your thread here. Funny how crafting a good post
sometimes leads to answering one's own questions.
My justification along your inquiry is the ability for the nodes to resolve
the transitive
Please ignore. After formulating this, I realized there is already an active
discussion on the topic and will follow up there.
Thanks, Brian
> On Feb 25, 2017, at 4:16 PM, Brian Topping wrote:
>
> Hi all,
>
> I'm putting together a packaging pattern for a clustered
Hi all,
I'm putting together a packaging pattern for a clustered app and am
wondering how others are doing things. I ran
across https://groups.google.com/d/msg/akka-user/4d2gVqFxHAU/1Zhp8JCVSBQJ
in research, in this post, Ryan indicates that they distribute all code to
all nodes and don't
Persistent Actor A consumes from Kafka and stores some events (let's call
them ProcessingRequested). Persistent Actor B runs a processing stream
whose source is tagged events from Persistent Actor A. As messages exit the
processing stream they are fed back to B which persists ProcessingSucceeded
Well, as the error message says you must make sure that the native libs are
in the directory specified by java.library.path (google to see how to do
that). But I'm not sure, because we run tests without specifying such path.
It could also be that the directory name contains spaces. Recipe for
I'm surprised that you say that it works with 2 ActorSystem and not with 1.
I would expect the problem to be opposite.
Passing an ActorRef owned by one ActorSystem to the other like you do in
your RunWithSeparateActorSystem can be problematic. Instead you should
acquire the ref with
You should use the BackoffSupervisor to handle such thing. Immediate
restart is typically not desired in case of persist failures.
/Patrik
fre 24 feb. 2017 kl. 10:42 skrev Andrey Onistchuk :
> Hello, guys!
>
> Recently I've came across the situation when my persisted cluster