Hi Matt,
On Wednesday, 15 January 2014 at 00:09, Matt Edwards wrote:
> Hey folks,
>
> thanks for the replies. And sorry for the delayed response. We are in the
> middle of a deployment, and things went a bit sideways, had to straighten it
> back out.
>
> I have read over the docs listed
Hey folks,
thanks for the replies. And sorry for the delayed response. We are in the
middle of a deployment, and things went a bit sideways, had to straighten
it back out.
I have read over the docs listed above, and they sound great, but I am a
bit lost on the implementation. I think the solut
Hi Ryan -
Why do you deploy the actors rather than starting up the actors on the
worker nodes and having them register with the master from there? Is it
to keep a proper supervision hierarchy?
Thanks,
On Saturday, January 11, 2014 5:00:49 PM UTC-5, Ryan Tanner wrote:
>
> Eric,
>
> We give e
Eric,
We give each node a role in its Akka config. The cluster-aware router for
that role (router is on the supervisor node) then remotely deploys routees
on those nodes so that we don't have to do so manually. Each routee only
does one piece of work at a time which it delegates to a "process
Hi Ryan - I'm curious to learn more about how you are using the
cluster-aware router and what it provides over the basic clustering
membership functionality.
Matt - we are also using a variation of "Balancing Workload Across Nodes"
(pre Akka Cluster) and it works great.
Thanks,
On Friday, Jan
We use that pattern in conjunction with clustering. We use a cluster-aware
router to deal with node membership within a worker role but we never
actually send messages to the router's ActorRef, we let the routees
register themselves with the "role leader" as we call it when they start.
On Frid
As an alternative to the cluster approach you could check out
http://letitcrash.com/post/29044669086/balancing-workload-across-nodes-with-akka-2
This pattern allows you to dynamically add (local or remote) workers to a
master actor.
Hendrik
Am Donnerstag, 9. Januar 2014 23:52:31 UTC+1 schr
We have an Akka cluster that might be relevant to your requirements.
Sounds like Akka clustering might suit your requirements very well. We
have an analytics process that can take up to 10 minutes per user depending
on how much data they have. We have a "supervisor" node in the cluster
which
