我创建了一个样本Akka.Cluster
,其中有三个节点A,B和C,其中A是灯塔。到目前为止,从日志中可以看出,当没有actor或者actor是本地的(使用spawn
和spawnOpt
创建)时,集群可以正常工作。我想从B创建一个actor并从C中访问它。
使用
let _ = spawne system "r-actor" <@ actorOf (fun msg -> printfn "Received: %s" msg) @> []
我得到了
2016-08-31 01:59:00.1185|INFO|Akka.Actor.EmptyLocalActorRef|Message String from akka://calculatorSystem/deadLetters to akka://calculatorSystem/user/r-actor was not delivered. 1 dead letters encountered.
使用
let r = FromConfig.Instance :> RouterConfig |> SpawnOption.Router
let _ = spawne system "r-actor" <@ actorOf (fun msg -> printfn "Received: %s" msg) @> [r]
抛出异常
Akka.dll中发生了
Akka.Configuration.ConfigurationException
类型的未处理异常 其他信息:Configuration problem while creating [akka://calculatorSystem/user/r-actor] with router dispatcher [akka.actor.default-dispatcher] and mailbox and routee dispatcher [akka.actor.default-dispatcher] and mailbox [].
Node C上的测试功能是
let rec calculate content =
printfn "Processing %s" content
let actor = select "/user/r-actor" system
actor <! content
let text = Console.ReadLine()
if text <> "quit" then
calculate text
calculate "sample1"
HOCON(节点B)
akka {
actor {
provider = "Akka.Cluster.ClusterActorRefProvider, Akka.Cluster"
serializers {
wire = "Akka.Serialization.WireSerializer, Akka.Serialization.Wire"
}
serialization-bindings {
"System.Object" = wire
}
deployment {
/user/add {
router = round-robin-pool
nr-of-instances = 10
cluster {
enabled = on
max-nr-of-instances-per-node = 10
allow-local-routees = off
}
}
/user/r-actor {
router = round-robin-pool
nr-of-instances = 10
cluster {
enabled = on
max-nr-of-instances-per-node = 10
allow-local-routees = off
}
}
}
}
remote {
log-remote-lifecycle-events = DEBUG
log-received-messages = on
helios.tcp {
transport-class = "Akka.Remote.Transport.Helios.HeliosTcpTransport, Akka.Remote"
applied-adapters = []
transport-protocol = tcp
hostname = "127.0.0.1"
port = 0
}
}
loggers = ["Akka.Logger.NLog.NLogLogger,Akka.Logger.NLog"]
cluster {
seed-nodes = [
"akka.tcp://calculatorSystem@127.0.0.1:7001"
]
roles = ["add-service"]
auto-down-unreachable-after = 10s
}
}
如何创建可由群集中的另一个节点调用的actor?
答案 0 :(得分:2)
定义路由器配置时,请勿使用/user
前缀 - 它会自动添加。
此外,如果你想选择驻留在另一个节点上的actor,你需要使用完整的actor路径(带有节点地址) - 由于事实,可能有不同的actor居住在不同的节点上同样的道路。你必须准确。
通常在编译时您不知道节点的地址。有两种方法可以提取它:
它更容易,但您无法对加入/离开节点做出反应。你每次都被迫检查它,这很慢。此示例使用ActorSelection.ResolveOne
来检索实际的IActorRef
实例。
async {
let members = Cluster.Get(system).State.Members
let actorRefs =
members
|> Seq.filter (fun m -> m.Roles.Contains("expected")) // use roles to filter out nodes that shouldn't be checked
|> Seq.map (fun m ->
let selection = select (m.Address.ToString() + "user/r-actor") system
let actorRef = selection.ResolveOne(timeout) |> Async.AwaitTask)
|> Async.Parallel }
在这里,您可以在节点加入/离开时做出反应。它还使用Identify
/ ActorIdentity
来接收实际的IActorRef
,这是更快的选择。
let aref =
spawn system "listener"
<| fun mailbox ->
let cluster = Cluster.Get (mailbox.Context.System)
cluster.Subscribe (mailbox.Self, [| typeof<ClusterEvent.IMemberEvent> |])
mailbox.Defer <| fun () -> cluster.Unsubscribe (mailbox.Self)
let rec loop () =
actor {
let! (msg: obj) = mailbox.Receive ()
match msg with
| :? ClusterEvent.MemberUp as up ->
// new node joined the cluster
let selection = select (up.Member.Address.ToString() + "user/r-actor") mailbox
selection <! Identify(null) // request actor under selection to identify itself
| :? ActorIdentity as id when id.Subject <> null ->
// actor has identified itself
id.Subject <! "hello"
| :? ClusterEvent.MemberRemoved as rem ->
// node leaved the cluster, invalidate all actors from that node
| _ -> ()
return! loop () }
loop ()
如果有疑问,我已经写了blog post关于从F#创建Akka.NET集群的问题。也许你会发现它很有用。