akka.net-cluster

问题 I want to have actors running on various processes (or nodes) send messages to other actors running off of different processes (or nodes), all while maintaining fault-tolerance and load balancing. I am currently attempting to use Akka.Cluster's Sharding feature to accomplish this. However, I am not sure how to accomplish this... I have the following code that reflects my seed node: let configurePort port = let config = Configuration.parse (""" akka { actor { provider = "Akka.Cluster

问题 I'm using Akka.NET's cluster (1.0.5) functionality to implement a service that consists of a master node that receives requests over HTTP and farms the work out to worker nodes that have joined the cluster. The idea is to be able to easily accomplish the following: add worker nodes to cluster when demand is high (check) be able to reboot the master node or take it offline (maintentance/misbehaviour/whatever) and have the workers reconnect when it becomes available (check) upgrade/reboot a

问题 After recent investigation and a Stack over flow question I realise that the cluster sharding is a better option than a cluster-consistent-hash-router. But I am having trouble getting a 2 process cluster going. One process is the Seed and the other is the Client. The Seed node seems to continuously throw dead letter messages (see the end of this question). This Seed HOCON follows: akka { loglevel = "INFO" actor { provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster" serializers {

问题 In my Akka.Net cluster I have several nodes. There is communication that I'd like to initiate when I've successfully joined the cluster. I can see in the log that I'm welcome to the cluster: Welcome from [akka.tcp://Animatroller@hakan-el:8899] but I can't see any events I can subscribe to that are raised for this. 回答1: Usually what you want in that case is to subscribe to ClusterEvent.MemberUp , which current actor will receive, once new node will become part of the cluster. Example of actor

问题 I'm creating a sample with Akka.Cluster with three nodes A, B and C where A is the lighthouse. So far, from the logs, the cluster works fine when there are no actors or when actors are local (created with spawn and spawnOpt ). I want to create an actor from B and access it from C. With let _ = spawne system "r-actor" <@ actorOf (fun msg -> printfn "Received: %s" msg) @> [] I get 2016-08-31 01:59:00.1185|INFO|Akka.Actor.EmptyLocalActorRef|Message String from akka://calculatorSystem/deadLetters

问题 I have a solution with 2 command line projects that creates an akka.net cluster with a seed and client process. The seed starts the cluster and then instantiates a consistent-hash-cluster-router that performs hash mapping on any message that implements my interface "IHasRouting". So any IHasRouting message (from the seed or client) should end up at seed on a routee for the hash of that message. The projects start fine and the cluster forms without error. Both seed and client instantiate a

问题 I am trying to build an actor system that can scale up/down based on the workload using the following configuration. akka { actor { serializers { wire = "Akka.Serialization.WireSerializer, Akka.Serialization.Wire" } serialization-bindings { "System.Object" = wire } deployment { /analysis { router = round-robin-pool routees.paths = ["/user/analysis"] resizer { enabled = on lower-bound = 1 upper-bound = 20 } } } } } in my main loop I am creating 3000 messages and pushing to the actors for

问题 I'm developing an Azure cloud service including multiple worker roles that form an akka.net cluster. How do I accomplish getting the cluster gossip and other messages end up in the compute emulator console windows? 回答1: At the moment I'm working on an Akka.NET cluster that will be hosted as Azure Cloud Services and ran into the same problem. The quickest way I found to accomplish this is to write a logging adapter (though I' still relatively new to Akka.NET, so take this advice with a pinch