On Sat, May 31, 2014 at 4:56 AM, Eugene Dzhurinsky jdeve...@gmail.com
wrote:
Hello!
I have a cluster with set of FSM actors deployed there. I also have a
*ClusterClient* configured to send a message to the dedicated actor
service, which then processes the passed data and now it has to
Shard rebalancing, as everything else, is managed for each entry type name
independently of other entry type names. There is one ShardCoordinator per
type name.
/Patrik
On Sat, May 31, 2014 at 11:45 PM, Luis Medina lu4...@gmail.com wrote:
Oops, in the second example I meant to say that Shard
Thanks!
--
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 received this message because you are subscribed to the Google Groups Akka
User List
Given that fact, I went ahead and implemented a ShardAllocationStrategy that
takes into account different entry types for figuring out what nodes to
create new entries in. First, I just want to describe the use-case that led
to me implementing this.
I'm working on a pipeline that will ingest
Hi Eduardo,
The ClusterSharding extension supports configuration of one role to use a
subset of nodes, but that is not what you are looking for. Instead of using
the ClusterSharding extension you may start the actors yourself and thereby
specify the roles.
See:
ShardCoordinatorSupervisor.props
I am running Scala Play 2.2.2 as the front end of for Java library. Certain
calls into the java library are extremely long running (order of hours).
I am looking for some mechanism to be able to run these calls
asynchronously but to also be able to cancel them once they have started,
I was clearly miss-configured.
I tried it again from the akka-sample-cluster-java activator template and
this has worked so I modified my configuration based on the word count
example.
And now things work.
Thanks
2014-05-29 8:12 GMT+01:00 Martynas Mickevičius
martynas.mickevic...@typesafe.com:
Many Thanks Patrik.
I'm afraid that if I manage the actors directly I'll lose all the cluster
benefits, include spreading out the mapping objectId - physical node. I
think that I can reduce the problem to a case where I could avoid the
creation of new actors in a particular node in the cluster
I strongly suggest reading through Effective Akka by Jamie Allen. He has
nice example of front-end to back-end design.
W dniu środa, 28 maja 2014 22:22:54 UTC+2 użytkownik Jabbar Azam napisał:
Hello,
I'm a bit confused with supervisor hierarchies. I've read the akka
documentation and
On Mon, Jun 2, 2014 at 1:10 PM, Eduardo Fernandes edu...@gmail.com wrote:
Many Thanks Patrik.
I'm afraid that if I manage the actors directly I'll lose all the cluster
benefits, include spreading out the mapping objectId - physical node.
That would not change. The ClusterSharding extension
Many Thanks Patrik for your time!
I'll check the addresses and let you know. With this info I could,
theoretically, implements a smooth node shutdown.
Best regards!
On Mon, Jun 2, 2014 at 3:12 PM, Patrik Nordwall patrik.nordw...@gmail.com
wrote:
On Mon, Jun 2, 2014 at 1:10 PM, Eduardo
Hey guys,
I would like to run an idea by the fine Akka community - which is to
discuss what it would take to turn Akka into a platform for building a
network of microservices: each one independently redeployable and easy to
change, yet through a common platform, take advantage of the
So 2.3 introduced changes that wreck havoc with those of us using Akka from
languages like Jruby. Namely being forced to pass java classes to props
instead of being able to pass instances.
stack overflow has a question about this that illustrates the problem:
It worked perfectly!
Many thanks for your help!
Regards.
El lunes, 2 de junio de 2014 15:24:58 UTC+2, Eduardo Fernandes escribió:
Many Thanks Patrik for your time!
I'll check the addresses and let you know. With this info I could,
theoretically, implements a smooth node shutdown.
Hi Martin,
I'm a little confused by your explanation. First you mention that ...the
affected database records are entity-specific... and no indexes are
touched. Hence, executing many Bookings in parallel causes no considerable
performance issues. But then you say that All of the bookings are
Hi Eduardo,
I recently implemented my own version of a ShardAllocationStrategy and made
use of the ShardRegion's addresses. I made a post about it
here: https://groups.google.com/forum/#!topic/akka-user/7p_fkEFJqHw
It doesn't solve your exact problem but maybe it will give you some ideas.
Nice post!
I'll use your concepts to implement the progressive scaling down.
Many thanks for your info!
On Mon, Jun 2, 2014 at 10:49 PM, Luis Medina lu4...@gmail.com wrote:
Hi Eduardo,
I recently implemented my own version of a ShardAllocationStrategy and
made use of the ShardRegion's
Hi,
I'm writing a very simple UDP server that echos messages back to a sender.
The sender tries to spam the server. When I run the client, I get a lot of
`Send(ByteString(..), NoAk(null))` responses. The UDP server literally
just echos the content back. It isn't doing any blocking compute.
On Monday, June 2, 2014 1:03:18 PM UTC-7, Chris Ochs wrote:
So 2.3 introduced changes that wreck havoc with those of us using Akka
from languages like Jruby. Namely being forced to pass java classes to
props instead of being able to pass instances.
stack overflow has a question about
Hey Evan, I'll bite...
I guess my first question would be to ask for a more clear definition of
what you mean by a microservice platform. It feels like this is trying to
tackle too many different pieces of the ecosystem when some are already
well-solved, while others just might not be
Hi Benoit,
in the upcoming 0.3 release there is a .mapFuture combinator that lets you
transform elements asynchronously.
Concerning the ActorSystem shutdown I do not understand your question, can you
rephrase?
Regards,
Roland
27 maj 2014 kl. 21:27 skrev benq benoit.quart...@gmail.com:
Hi,
Hi Steven,
thanks for this write-up, your analysis is thorough and correct on all counts.
Remoting needs to use a simplistic approach to the coroner problem (i.e. when
to declare another system “dead”—and zombies are not tolerated), which is
mostly just a timeout that you should set high
Hi Adriano,
how do you determine the node’s capabilities? Can they change at runtime?
Regards,
Roland
30 maj 2014 kl. 15:49 skrev Adriano Machado adriano.mach...@gmail.com:
Hi.
My question is based on the Activator template akka distributed workers. I
have started with it and
Hey,
I want to create a Timer Actor that tracks the progress of the entire
program (and also estimate remaining execution time). Since the timer actor
will have to hold mutable variable aka current progress, I think it
should be constructed under the highest supervisor instead of being
Hi Kenneth,
the current state of Akka Streams is that we want to get the functionality
implemented in a correct fashion first and optimize later. You are right that
optimistic write-through would be more performant, but the implementation of
that scheme requires a lot more care because on the
25 matches
Mail list logo
