Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

Hello again! After the further reading about Akka, it seems that I'm trying to re-implement some Java enterprise patterns over Akka, which is not neccessary for my case. Actors seems to be very lightweight but the nature, so its rather a desired way to have hundreds of actors. managing their ow

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

On Fri, May 09, 2014 at 05:18:09PM -0700, Ryan Tanner wrote: > I think you misunderstood what cluster events are for. > > MemberUp/Down aren't fired when your actors come up, they're fired when a > new member joins the cluster. If you want an actor to know when another > actor is ready, you nee

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

I think you misunderstood what cluster events are for. MemberUp/Down aren't fired when your actors come up, they're fired when a new member joins the cluster. If you want an actor to know when another actor is ready, you need to explicitly send a message. You can however use DeathWatch to kno

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

Roland, many thanks for the reply! As far as I understood, the proposed (and desired) way to partition a task across a cluster is to let the *worker* actors to *pull* a chunk of a task from a *task actor* instead of having the task actor to *push* the chunk of data to the *workers*. This sound

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

8 maj 2014 kl. 23:06 skrev Eugene Dzhurinsky : > On Thu, May 08, 2014 at 10:37:21PM +0200, Akka Team wrote: >> Hi Eugene, >> >> could you clarify the use-case a bit more? Why would there be multiple >> FSMs, where would the messages to be processed come from, why can’t you use >> the work pullin

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

On Thu, May 08, 2014 at 10:37:21PM +0200, Akka Team wrote: > Hi Eugene, > > could you clarify the use-case a bit more? Why would there be multiple > FSMs, where would the messages to be processed come from, why can’t you use > the work pulling > pattern

Re: [akka-user] Try-and-lock an FSM actor in a cluster, anything better?

Hi Eugene, could you clarify the use-case a bit more? Why would there be multiple FSMs, where would the messages to be processed come from, why can’t you use the work pulling pattern ? One thing to note: saying “l

[akka-user] Try-and-lock an FSM actor in a cluster, anything better?

Hello! I need to have a set of FSM front-end actors in the cluster. I want to be able to recognize what state does the actor has for the moment, to decide if this actor could be used to process a message (it's in the *Accept*state). The ony thing I can think about is to get a list of all actors