[akka-user] Cluster failover: preloaded actors

Hi All. First of all many thanks for so efficient library. Very good job! We're analyzing Akka to support a cluster of heavy objects (a single actor could have a couple of gigs in RAM). I'm wondering if I could use some kind of 'preloaded' in ram slave actor that could be used if the 'master

Re: [akka-user] Cluster failover: preloaded actors

Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously to two processors (the main and a standby) and in case of timeout talking to the first we could talk to the second. After the main recovering we could return to the original situation. Maybe we could

Re: [akka-user] Cluster failover: preloaded actors

will implement it, but we will take it into consideration. Thanks for the feedback. Cheers, Patrik On Tue, Mar 18, 2014 at 8:52 PM, Eduardo Fernandes edu...@gmail.comjavascript: wrote: Many thanks Patrik for your post. Good shot. We could consider sending commands simultaneously

[akka-user] Cluster/remote pipeline strategy

Hi all. We have a system where we've implemented a pipeline strategy as follows: 1) If the number of messages pending for all actors to a remote host is more than N we flush the message queue to the net 2) If the total number of blocked threads waiting for reading is more then N we flush the

Re: [akka-user] Cluster/remote pipeline strategy

El jueves, 20 de marzo de 2014 09:44:28 UTC+1, Patrik Nordwall escribió: Hi Eduardo, Many thanks for your time, Patrik. On Thu, Mar 20, 2014 at 12:04 AM, Eduardo Fernandes edu...@gmail.comjavascript: wrote: Hi all. We have a system where we've implemented a pipeline strategy

Re: [akka-user] Cluster/remote pipeline strategy

Many thanks Patrik for the info!! I'll check the links you mentioned. I think you're right, the frameworks could improve a lot our performance. Best regards!! El jueves, 20 de marzo de 2014 13:13:28 UTC+1, Patrik Nordwall escribió: On Thu, Mar 20, 2014 at 12:25 PM, Eduardo Fernandes

Re: [akka-user] Low performance in cluster + sharding with single actor

, eventually GC kicks in due to continuously increasing memory usage. -Endre On Tue, Mar 25, 2014 at 11:00 AM, Vitaliy V. Shopov shopov@gmail.comjavascript: wrote: And what is your updated benchmark result?) 2014-03-25 13:57 GMT+04:00 Eduardo Fernandes edu...@gmail.comjavascript

[akka-user] Akka cluster failover: hot swaping

Hi all. I'm trying a hot swap between an active processor and a backup one, in line with the thishttps://www.assembla.com/spaces/akka/tickets/3938#/activity/ticket: ticket, to avoid delay while swapping huge actors. I'm thinking about manually sending my commands to two different actors in

[akka-user] [Cluster] Strange error with simultaneous messages

Hi. First of all, thanks for your time reading this. I'm working with an Akka cluster and I don't understand a peculiar effect I'm observing. If I send 70 simultaneous messages (and for each message a callback resend the message again) everything works fine. But if I try the same with 100

[akka-user] Re: [Cluster] Strange error with simultaneous messages

For sure... Akka version 2.3.2! -- 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

[akka-user] Cluster, sharding and roles

Hi all. Probably this is a silly question but I couldn't find any clear answer in the group or docs. Suppose I have a cluster with 4 nodes with 2 roles (2 node instances per role). How could I create two shardings, each one sending messages to the nodes belonging to a particular role? The

Re: [akka-user] Cluster, sharding and roles

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

Re: [akka-user] Cluster, sharding and roles

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

Re: [akka-user] Cluster, sharding and roles

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

Re: [akka-user] Re: Cluster, sharding and roles

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

[akka-user] Akka cluster: stopping actor doesn't remove sharding entry

Hi. First of all thanks for your time on this. I'm using Akka version 2.3.4 (Java). I've stopped an actor getContext().stop(getSelf()); and when I look at the rebalance() method in my AllocationStrategy I still see the entry in the sharding region corresponding to the stopped actor.

Re: [akka-user] Akka cluster: stopping actor doesn't remove sharding entry

Many thanks for your help Endre. Completely understood from shard perspective. I'll check if the entry disappear if the actor is stopped (which is not the case for the sharding). Regards. El miércoles, 23 de julio de 2014 11:13:46 UTC+2, Akka Team escribió: Hi Eduardo, Shards are assumed

Re: [akka-user] Akka cluster: stopping actor doesn't remove sharding entry

Ok. Entries are managed as expected. After looking at the code I understand what you mean. Thanks a lot for your help. Regards. El miércoles, 23 de julio de 2014 15:41:00 UTC+2, Eduardo Fernandes escribió: Many thanks for your help Endre. Completely understood from shard perspective

Re: [akka-user] Akka cluster: stopping actor doesn't remove sharding entry

although no actors might be running in that shard. In fact this table is persisted by the ShardCoordinator so if the node hosting it fails it can be reliably restored in a new node. -Endre On Thu, Jul 24, 2014 at 12:42 AM, Eduardo Fernandes edu...@gmail.com wrote: Ok. Entries are managed

Re: [akka-user] Akka cluster: stopping actor doesn't remove sharding entry

-Endre -Endre On Thu, Jul 24, 2014 at 11:27 AM, Eduardo Fernandes edu...@gmail.com wrote: Yes, we are using passivation. Tx. There is a way of retrieve the entries id's from the shardings? There is a member called entries in the sharding region class but I don't know if I have access

[akka-user] AllocationStrategy rebalance() is stopping actors outside resharding list

Hi. We're using Akka 2.3.13 (Java Interface). We have our own AllocationStrategy implementation and the idea is move several shards from one node to other. We have a 2 nodes in the cluster and 1000 shards in total. When we start 7000 actors we have approximately 3500 actors on each node

[akka-user] Akka cluster: Passivation + reshard

Hi. Suppose that we have all actors of a particular shard passivated. The next time an actor of that shard receive a message the new incarnation will be in the same physical node where the shard was before or the the logic of new shard is triggered again and the shard is created for example

Re: [akka-user] awaitTermination not working?

()/awaitTermination() have no effect when those external threads are running. Probably when we migrate to 2.4 the problem will just vanish. Thanks again! El viernes, 11 de marzo de 2016, 13:45:59 (UTC+1), Eduardo Fernandes escribió: > > Me too :( > > I'l prepare a minimum example. Typical

Re: [akka-user] awaitTermination not working?

Hi Roland. Thanks for your answer. Sure, the problem was that I was not aware about that threads. I'm afraid that I have to shutdown such threads at system shutdown because the library shares threads among several actor instances. Anyway, problem solved! Thanks again for your time very helpful

[akka-user] awaitTermination not working?

Hi group! Thanks for your time in advance. I'm using Java version 2.3.13. In my JUnit tests and when I'm testing in single node the awaitTermination function after the traditional shutdown() is not awaiting for the actor system termination. In fact the actorsystem is not event starting to

Re: [akka-user] awaitTermination not working?

rmination. > (note that awaitTermination is replaced by something else in 2.4.x, see > deprecation) > > In TestKit there is a helper method to shutdown the actor system, await > and verify. > > On Fri, Mar 11, 2016 at 1:22 PM, Eduardo Fernandes <edu...@gmail.com> &g

Re: [akka-user] awaitTermination not working?

the place > so I'm pretty sure your code is not correct. > > On Fri, Mar 11, 2016 at 1:39 PM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Hi. Thanks Patrik. >> >> I am using shutdown() and then awaitTermination(). Both don't block and >>

Re: [akka-user] awaitTermination not working?

Hi. Hum... I think that is not the case. In fact the methods shutdown() and awaitTermination() simply don't block at all and the next test says that the port 12551 is already bound. If my previous test starts two nodes everything works find and the awaitTermination() method waits for the node

Re: [akka-user] Akka cluster: Passivation + reshard

e shard goes away, so next message will > trigger allocation of the entity actor where the shard is currently > located. Rebalancing can change the current location. > > /Patrik > > On Mon, Feb 29, 2016 at 10:30 AM, Eduardo Fernandes <edu...@gmail.com> > wrote: > &g

Re: [akka-user] Is it possible to increase the number of serialization threads?

class names etc. > > On Sat, Jul 2, 2016 at 1:14 AM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Hi. >> >> I'm using Akka 2.3.13, Java edition. >> >> I'm making some performance tests and in the same machine with 8 cores I >> see that the

Re: [akka-user] Is it possible to increase the number of serialization threads?

tting in > your readObject/writeObject? > What overhead are you observing compared to using a custom Serializer? > > On Sat, Jul 2, 2016 at 10:02 PM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Hi. >> >> If you have writeObject/readObject defined in you

Re: [akka-user] Re: Is it possible to increase the number of serialization threads?

;>> } >>> >>> Also, what serialization are you using? Hopefully is the not default >>> Java serialization, most people use Kryo serialization. >>> >>> Non-related but could help: >>> >>>- Set Akka version to "2.3.15" (n

Re: [akka-user] Re: Is it possible to increase the number of serialization threads?

related but could help: >>> Set Akka version to "2.3.15" (next week 2.3.16 is probably going to be >>> released) >>> Set Netty version to "3.10.6.Final" which will be part of next release. >>> See https://github.com/netty/netty/issues?q=milestone%3

Re: [akka-user] Is it possible to increase the number of serialization threads?

>> >> Regards >> >> On Sat, Jul 2, 2016 at 10:05 PM, Viktor Klang <viktor.kl...@gmail.com> >> wrote: >> >>> Hi Eduardo, >>> >>> Perhaps I misunderstood, what serialization format are you emitting in >>> your readObject

Re: [akka-user] Is it possible to increase the number of serialization threads?

log-remote-lifecycle-events = off >> >> netty.tcp { >> >> server-socket-worker-pool { >> pool-size-min = 4 >> pool-size-factor = 1 >> pool-size-max = 8 >> } >> >> client-socket-worker-pool { >>

Re: [akka-user] Is it possible to increase the number of serialization threads?

ere aren't any synchronized-blocks or locks > used? (i.e. is this a contention problem rather than a paralellization > problem?) > > On Sun, Jul 3, 2016 at 12:28 PM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Ups... sorry for misunderstanding your question. >>

Re: [akka-user] Is it possible to increase the number of serialization threads?

) at com.esotericsoftware.kryo.serializers.CollectionSerializer.read(CollectionSerializer.java:22) at com.esotericsoftware.kryo.Kryo.readObject(Kryo.java:682) at com.esotericsoftware.kryo.serializers.ObjectField.read(ObjectField.java:106) ... 32 more On Sun, Jul 3, 2016 at 3:43 PM, Eduardo Fernandes <edu...@gmail.com> wrote: > Ok. Tha

Re: [akka-user] Is it possible to increase the number of serialization threads?

ster classes automatically not listed. > > HTH, > > Guido. > > On Sunday, July 3, 2016 at 10:39:50 PM UTC+1, Eduardo Fernandes wrote: > >> Hi All. >> >> I'm using akka-kryo-serialization_2.10 with incremental strategy. I'm >> using 2.10 for everything so maybe

Re: [akka-user] Is it possible to increase the number of serialization threads?

b/artery-dev/akka-remote-tests/src/multi-jvm/scala/akka/remote/artery/MaxThroughputSpec.scala > > With new remoting (Artery) that test performs around 700.000 msg/s on my > local machine. > > > On Mon, Jul 4, 2016 at 8:54 AM, Eduardo Fernandes <edu...@gmail.com> > wro

Re: [akka-user] Is it possible to increase the number of serialization threads?

Nordwall <patrik.nordw...@gmail.com> wrote: > > > On Mon, Jul 4, 2016 at 12:09 AM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Ok. I'll manage to change from 2.10 to 2.11. Yes, my project is in Java. >> We're using Java 8 but the transition to 2.4 is n

Re: [akka-user] Is it possible to increase the number of serialization threads?

AM, Patrik Nordwall <patrik.nordw...@gmail.com> wrote: > Are you talking about 1.000.000 (500.000) messages/s over the network or > what is your definition of transaction? > > On Mon, Jul 4, 2016 at 8:47 AM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >

Re: [akka-user] Is it possible to increase the number of serialization threads?

sprint. Best regards Patrik. On Mon, Jul 4, 2016 at 9:18 AM, Patrik Nordwall <patrik.nordw...@gmail.com> wrote: > > > On Mon, Jul 4, 2016 at 9:13 AM, Eduardo Fernandes <edu...@gmail.com> > wrote: > >> Wow!!! I have to try the new remoting! >> >>

Re: [akka-user] Is it possible to increase the number of serialization threads?

> > On Monday, July 4, 2016 at 6:56:25 AM UTC+1, Patrik Nordwall wrote: >> >> >> >> On Mon, Jul 4, 2016 at 12:09 AM, Eduardo Fernandes <edu...@gmail.com> >> wrote: >> >>> Ok. I'll manage to change from 2.10 to 2.11. Yes, my project is in Jav

[akka-user] Is it possible to increase the number of serialization threads?

Hi. I'm using Akka 2.3.13, Java edition. I'm making some performance tests and in the same machine with 8 cores I see that the serialization process is my bottleneck. I know that because after an increment of actor cpu usage the throughput is exactly the same. My actor system talks to 2

Re: [akka-user] Max number of cluster nodes

case in more detail, can > you talk about it openly or would you prefer to talk in private, > if so please ping me on kt...@lightbend.com , thanks! > > — Konrad > > > On 30 June 2017 at 02:59:12, Eduardo Fernandes (edu...@gmail.com > ) wrote: > > Hi Konrad. Thanks fo

Re: [akka-user] Max number of cluster nodes

cally you would run one or a few JVMs on > one machine (EC2/GCE instance). > > Do you mean nodes in that sense, or do you mean actors? > > On Thu, Jun 29, 2017 at 8:15 PM, Eduardo Fernandes <edu...@gmail.com > > wrote: > >> Hi again. >> >> I'm talking a

[akka-user] Max number of cluster nodes

Hi all. I'm starting a new project and I'm wondering about what is the recommended max number of nodes in an Akka cluster. I've read numbers around 2400 in this test but with the new Artery

Re: [akka-user] Max number of cluster nodes

c? > > — Konrad > > > On 30 June 2017 at 02:43:43, Eduardo Fernandes (edu...@gmail.com > ) wrote: > > Hi all. > > I'm starting a new project and I'm wondering about what is the recommended > max number of nodes in an Akka cluster. I've read numbers around 2400 in this &

[akka-user] Cluster: Loosing messages when rebalancing

Hi all. I'm using Akka 2.3.13 [I know... a bit old :( ] with Java. A few times I'm loosing messages (in a very intensive concurrent environment). In my case a message is sent to the actor just before the postStop() method is called, indicating that the kill action is sent to it due the

[akka-user] Re: Cluster: Loosing messages when rebalancing

Johannes > > On Friday, September 22, 2017 at 6:02:48 PM UTC+2, Eduardo Fernandes wrote: >> >> Hi all. >> >> I'm using Akka 2.3.13 [I know... a bit old :( ] with Java. >> >> A few times I'm loosing messages (in a very intensive concurrent >> e

[akka-user] Mixing shard regions and proxy to shards regions in the same actor system

Hi all. I had this working with java version 2.3.13 and after moving to 2.5.6 it stop working. Let me explain the topology. In configuration I have akka.cluster.sharding { role = "backend" } Ok then. If in a process (frontend) I use startProxy and in other process (backend) I use start in

Re: [akka-user] Re: Mixing shard regions and proxy to shards regions in the same actor system

Fine!! It works like a charm!! Many thanks Patrik for your time on this!! I'm attaching the code fixed with your comments. Many thanks for your time on this. It was not clear for me that the role was mandatory. I supposed that a non-role means any. My fault. Happy Halloween and thanks again!

Re: [akka-user] Akka 2.5.8 (Java Edition) Error initializing: java.lang.IllegalStateException: not yet initialized

s to Akka >> dependencies. >> >> Akka Streams and Actor etc should all be on the same version. >> >> -- >> Cheers, >> Konrad 'ktoso <http://kto.so>' Malawski >> Akka <http://akka.io/> @ Lightbend <http://lightbend.com/> >> >>

Re: [akka-user] Akka 2.5.8 (Java Edition) Error initializing: java.lang.IllegalStateException: not yet initialized

Fixed. As you've said there was a mix in initialization. I was using persistence jdbc version 3.0.0 which loaded an old version of the stream jar. After changing to 3.1.0 the problem was fixed. Many thanks for you time Patrik. Regards. -- >> Read the docs:

[akka-user][deprecated] Acordes

https://ukutabs.com/o/oasis/wonderwall/?transpose=-2#point -- * ** New discussion forum: https://discuss.akka.io/ replacing akka-user google-group soon. ** This group will soon be put into