Thanks Patricks,
I will use Backoff.onStop method to create the supervisors for the
aggregates and try to restart them incrementally in time.
Sebastian.
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/addit
It's right that when you use Cluster Sharding you will not build deep actor
hierarchies. The main purpose of the hierarchy is supervision, how to deal
with failures. The entities are already managed by Cluster Sharding. You
may still add a supervisor actor between Cluster Sharding and the actual
en
I´ve read that in order for an akka based software to be well organized and
supervised it is recommended to organize actors as a tree instead of having
top level actors hanging from the User guardian and this is something I
still don´t get the point. I see the point from a performance tip when
Hi,
Recently we've been setting up some testing of our application when running
as a Cluster. We start 1 actor system on port 2551 as part of our test
suite.
As part of this individual test we then start further servers on port 2552
and 2553.
This works great - we have a counting actor that show
On Thu, Sep 24, 2015 at 6:59 PM, wrote:
> I am trying to set up an akka Cluster that includes a ClusterSingleton,
> ClusterSingletonManager and ClusterSingletonProxy which in turn seems to
> necessitate using a ClusterClient, ClusterReceptionist and
> DistributedPubSubMediator.
>
ClusterSingleto
I am trying to set up an akka Cluster that includes a ClusterSingleton,
ClusterSingletonManager and ClusterSingletonProxy which in turn seems to
necessitate using a ClusterClient, ClusterReceptionist and
DistributedPubSubMediator.
I am more or less following the typesafe activator code, but it
Hi Paul,
Curious to know which monitoring tool you employed?
-Prakhyat M M
On Saturday, 23 August 2014 19:32:05 UTC+5:30, Paul Cleary wrote:
>
> Thanks Ronald and Heiko. Turns out, the code that was doing the
> monitoring \was the culprit.
>
> I removed my monitoring, and everything took off f
Thanks Ronald and Heiko. Turns out, the code that was doing the monitoring
\was the culprit.
I removed my monitoring, and everything took off from there. I am
considering this issue closed, I appreciate your help.
On Saturday, August 23, 2014 8:09:25 AM UTC-4, rkuhn wrote:
>
>
> 23 aug 2014
Sounds like a possible visibility issue from the description.
On Aug 23, 2014 2:09 PM, "Roland Kuhn" wrote:
>
> 23 aug 2014 kl. 02:37 skrev Paul Cleary :
>
> I have an actor system that is setup using all of the akka defaults.
>
> Nothing in the system has a lot of latency, we are talking about s
23 aug 2014 kl. 02:37 skrev Paul Cleary :
> I have an actor system that is setup using all of the akka defaults.
>
> Nothing in the system has a lot of latency, we are talking about sub
> millisecond (20 microsecond) latencies.
>
> All traffic flows through a single actor to downstream actors.
While this is sort of speculative, it looks like you have introduced a
bottleneck. Maybe you can use a router for your main actor, resulting in
parallelizing entry work (assuming you have multiple cores and enough threads)?
Heiko
On 23 Aug 2014, at 02:37, Paul Cleary wrote:
> I have an actor
I have an actor system that is setup using all of the akka defaults.
Nothing in the system has a lot of latency, we are talking about sub
millisecond (20 microsecond) latencies.
All traffic flows through a single actor to downstream actors. This "main"
actor just forwards the message onto chil
Then how would I get a reference to these Actor systems over remoting?
On Thursday, 26 December 2013 21:55:01 UTC+5:30, Akka Team wrote:
>
> Hi Amit,
>
>
> On Thu, Dec 26, 2013 at 4:19 PM, Amit Mula
> > wrote:
>
>> I have a small query,
>>
>> what happens if I create multiple Actor Systems with s
Hi Amit,
On Thu, Dec 26, 2013 at 5:57 PM, Amit Mula wrote:
> Then how would I get a reference to these Actor systems over remoting?
>
You need the host/port information of the remote system, then you can use
ActorSelection to look up any particular ActorRef. See:
http://doc.akka.io/docs/akka/2
Hi Amit,
On Thu, Dec 26, 2013 at 4:19 PM, Amit Mula wrote:
> I have a small query,
>
> what happens if I create multiple Actor Systems with same name like
>
> ActorSystem _system1 = ActorSystem.create("multi");
>
> ActorSystem _system2 = ActorSystem.create("multi");
>
> ActorSystem _system3 = A
I have a small query,
what happens if I create multiple Actor Systems with same name like
ActorSystem _system1 = ActorSystem.create("multi");
ActorSystem _system2 = ActorSystem.create("multi");
ActorSystem _system3 = ActorSystem.create("multi");
Will there be separate instances in the JVM o
16 matches
Mail list logo
