Hi Heiko - yes. I did read the docs before consulting the source. I was
unsure if the timeout included retries.
Thank you for the clarification.
On Monday, April 7, 2014, Heiko Seeberger wrote:
> Eric,
>
> The source never lies. If that doesn't convince you, take a look at the
> docs:
>
> "Res
Eric,
The source never lies. If that doesn't convince you, take a look at the docs:
"Resolve the ActorRef matching this selection. The result is returned as a
Future that is completed with the ActorRef if such an actor exists. It is
completed with failure ActorNotFound if no such actor exists o
On Friday, March 21, 2014 5:37:11 PM UTC, Ryadh khsib wrote:
>
> Hi all,
>
>
> We are getting intermittently a "[actor name [joinSeedNodeProcess] is not
> unique!]" exception at the akka Cluster system start up.
>
> The production setup is a akka Singleton cluster deployed on 12 tomcats
> acro
Hi guys:
Does actorSelection(path).resolveOne(timeout) retry? For example, if it is
called before the target actor is started, but the target actor does get
started before the timeout elapses.
>From the source it doesn't look like it but I may not be looking hard
enough.
Thanks,
--
>>>
typo, I meant: "... not obvious from the docs"
-- k
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.google.com/group/akka-user
---
You r
Hello Chanan,
What Heiko said +1 :-)
The EventBus is strictly *local-only*, the reasons for that have been
explained a bit here:
https://groups.google.com/forum/#!searchin/akka-user/eventstream$20local/akka-user/gSO7s6587BQ/WQZGCGJrfq4J
Thanks for pointing out that it's not from the docs (
http:/
Chanan,
Nope, the event bus is a local thing. Of course you could start a cluster aware
actor on each node that subscribes to the event bus and forwards events to
cluster mates, but that's something you have to build on your own.
Heiko
On 07 Apr 2014, at 21:17, Chanan Braunstein
wrote:
> He
Hello,
I didn't find this in the documentation - Do message published on an
EventBus go to the whole cluster?
Thanks,
Chanan
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>
Hi,
Anyone have an example SupervisoryStrategy that is implemented in Java?
We want to be able to detect when Akka doesn't restart a child after it
fails 'x times in y minutes' and the 'handleChildTerminated' looks like the
correct place. (We want to alert production operations that something m
Thanks! :)
On Monday, April 7, 2014 11:23:09 AM UTC-7, Ryan Tanner wrote:
>
> It was discussed last week ;)
>
> https://groups.google.com/forum/#!topic/akka-user/zPJOLe0V760
>
> On Monday, April 7, 2014 10:36:11 AM UTC-6, Scott Clasen wrote:
>>
>> From my testing I see that FSMs dont fire transiti
Thanks Konrad -
I have an app that launches cluster members by ssh-ing into each box and
running a script.
The launcher app is joining the cluster to simplify the logic of knowing
when everything is up. I had a different actor system name for the
launcher because it's a different app. But it's
It was discussed last week ;)
https://groups.google.com/forum/#!topic/akka-user/zPJOLe0V760
On Monday, April 7, 2014 10:36:11 AM UTC-6, Scott Clasen wrote:
>
> From my testing I see that FSMs dont fire transitions on stay() or
> goto(SameState).
>
> I haven't found any docs that say that why tha
Hi Bjorn,
Thanks a lot for getting back to me. I was able to try out the
ConsistentHashoungRouter as per your suggestion and worked really nice. We
did a little stress test over last week and worked as expected.
Thanks again for all the help.
Meena
On Tuesday, April 1, 2014 4:20:59 AM UTC-4,
>From my testing I see that FSMs dont fire transitions on stay() or
goto(SameState).
I haven't found any docs that say that why that might be, but it seems like
it would be nice and more symmetric if they did.
Has this been discussed in the past?
--
>> Read the docs: http://akka
Hi Boris,
I dug a little bit deeper and it seems to be a bug in a Balanced Router
code. I have created an issue for this. You can track it
at:
https://www.assembla.com/spaces/akka/tickets/3981-balancingpool-uses-disallowed-characters-for-the-dispatcher-config-path#/activity/ticket:
Martynas
-
Hi,
I've been playing around with Akka for a bit in order to see if it will be
a good fit for my project.
I have some basic concerns before I get going and I was just wondering if
anyone here had
already done something similar or if you could point me in the right
direction. So on to the proj
Hello Eric,
Is having the same actor system name required?
>
Yes, for a cluster to converge the cluster members should have the same
actorsystem-name.
I like to think of it as: the ActorSystem being the “universe” in which
Actors live, the cluster just allows them to live on different “planets”
(
Hello there Andriy,
I think Christian on StackOverflow has already answered most questions
already :-)
As for the the “initialization dance” going on with Actors - there’s a few
patterns that can help:
http://doc.akka.io/docs/akka/2.3.1/scala/actors.html#initialization-patterns
But in general
Sriram:
After some time:), what did you end up with? Could you share any experience?
--
>> Read the docs: http://akka.io/docs/
>> Check the FAQ:
>> http://doc.akka.io/docs/akka/current/additional/faq.html
>> Search the archives: https://groups.googl
19 matches
Mail list logo