Re: [akka-user] flexible path router

> On 29 Feb 2016, at 20:17, Viktor Klang wrote: > > Actors can process millions of messages per second. What are your > requirements? > At present that should do, as I am just building up an initial platform for a distributed social web. But longer term you can think

Re: [akka-user] flexible path router

Actors can process millions of messages per second. What are your requirements? -- Cheers, √ On Feb 29, 2016 2:05 PM, "Henry Story" wrote: > Hi, > >I am writing an Http Server where each resource on the file system is > the responsibility of an actor. > To keep it

[akka-user] Re: flexible path router

I opened akka issue 19919 for this, as it seems to me that there is a small piece of functionality missing, that it would not be that difficult to add, namely something like context.actorReach(path) to find the ActorRef for the actor or its closest

Re: [akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

Sure. https://github.com/akka/akka/issues/19917 it is. On Mon, Feb 29, 2016 at 5:17 PM, Endre Varga wrote: > > > On Mon, Feb 29, 2016 at 5:03 PM, Bert Robben > wrote: > >> I kill the node (to simulate that the node crashes); the cluster detect

Re: [akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

On Mon, Feb 29, 2016 at 5:03 PM, Bert Robben wrote: > I kill the node (to simulate that the node crashes); the cluster detect > this as unreachable and because I have auto-down configured as "yes", the > master DOWNs it after some seconds (I have

Re: [akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

Having thought a bit further on this. Given the fact that ddata writemajority/readmajority replication is not guaranteed to be consistent, I'm having even more doubts on the behavior of sharding based on ddata in case of severe node failures in the cluster. Any simple solutions for this?

Re: [akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

I kill the node (to simulate that the node crashes); the cluster detect this as unreachable and because I have auto-down configured as "yes", the master DOWNs it after some seconds (I have auto-down-unreachable-after = 10s). I see this clearly in the logs that the node is DOWN'ed. And I wait

Re: [akka-user] [akka-stream] tcp retransmission?

Thanks. I am going to write something outside the JDK to test it out. Maybe I have a confused IP stack, who knows. On Monday, February 29, 2016 at 2:21:36 AM UTC-6, drewhk wrote: > > Hi Val, > > I don't really know what is going on there, Akka works via JDK NIO and > have no access to that

Re: [akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

Well, when you say "remove" nodes, do you actually DOWN them, or you just let them be marked UNREACHABLE? I think the issue might be that Akka Cluster does treat UNREACHABLE nodes as still part of the cluster and hence they count against majority decisions. DOWN-ing them removes them from the

[akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

That is my experience - but I do strange things, like rolling restarts. -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >> http://doc.akka.io/docs/akka/current/additional/faq.html >> Search the archives:

[akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

So should I read this as "sharding with ddata is not usable in small clusters with unreliable nodes" ? That would be a bummer. On Monday, February 29, 2016 at 2:42:43 PM UTC+1, Marek Żebrowski wrote: > > I had similar problem - basically shardcoordinator needs to read data from > Majority of

[akka-user] Re: DDShardCoordinator gets confused after some nodes are removed

I had similar problem - basically shardcoordinator needs to read data from Majority of the nodes - it seems impossible in small cluster when nodes are added/removed -- >> Read the docs: http://akka.io/docs/ >> Check the FAQ: >>

[akka-user] flexible path router

Hi, I am writing an Http Server where each resource on the file system is the responsibility of an actor. To keep it simple, there are at least two types of actors: one responsible for directories and one responsible for files. Directory actors will be actors with children and files will

[akka-user] DDShardCoordinator gets confused after some nodes are removed

Hi, I'm getting strange results when using sharding with state-store-mode = ddata. This is my scenario: * I have a cluster with 4 nodes (A1, B1, A2, B2). In this cluster there are 3 shards: - I have one set of primary actors sharded across all these nodes (A1, B1, A2, B2). - I also have

Re: [akka-user] Re: Akka persistence with AtLeastOnceDelivery - Replay only unconfirmed messages

Thanks Patrick. It did the trick. On Friday, 26 February 2016 18:59:58 UTC+5:30, Patrik Nordwall wrote: > > You can save snapshot to reduce number of replayed events. Note > documentation around snapshots and AtLeastOnceDelivery. > > > > On Fri, Feb 26, 2016 at 6:23 AM, Ganta Murali Krishna

[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] [akka-stream] tcp retransmission?

Hi Val, I don't really know what is going on there, Akka works via JDK NIO and have no access to that low level TCP features. In other words, I really don't know what is going on on your machine and why you are seeing it, but I don't think we can do anything about it. -Endre On Mon, Feb 29,