These are chat archives for akkadotnet/akka.net
@corneliutusnea this sounds more like an Azure than Akka problem ;) Also: you can use any technique to form a cluster - lighthouse is basically a stub actor system with no capabilities - only thing needed is address of at least one other service, that is part of the cluster itself (in case when cluster is not formed yet, you can initialize it by calling
cluster.Join(cluster.SelfAddres). The only issue is how are you going to receive first seed node addresses when they are dynamic.
In core repo, within Cluster.Sharding example I've created a simple service which shares node addresses used for cluster bootstrapping and uses shared sqlite db for that. Only downside is that it doesn't react on hard (ungraceful) shutdown of the node - that node is not removed from records. In scala one of the examples for similar solution could be Akka.Cluster.Etcd
Does akka.net have options more detailed than a "heartbeat" to know if an actor system is "healthy"? I am evaluating using it for my compay and I am worried that it will not handle the scenarios that I have. Specifically, a server is at 98% utilization and is going to be very slow doing most anything. Except a heartbeat. It will respond just fine to a simple "ping".
Is there a plugin or option to check more than just a heartbeat during routing?