If these nodes supposed to gain separate gating duration each like First - 1d; Second - 1s then there should be two distinc NodeConfig calls per each role
mind submitting a PR to fix that?
yeah, that'd be wrong then
I'm going to pay tech debt regarding our discussion about obsolete regexp in #2502
So I can carry it too
But surprisingly this spec is passing all this time lol
for the people who are interested. The serilog logger plugin has been updated to 1.1.3
Hi guys! Have a question about new hyperion serializer. We are using actively Akka.Cluster.Tools and Akka.Cluster.Sharding. Can we swtich to hyperion from wire right now, or we should wait for special update of Akka.Cluster.Tools?
there are some inconsistency in docs
Starting from Akka.NET v1.5, default Newtonsoft.Json serializer will be replaced in the favor of Hyperion. At the present moment, wire is required by some of the newer plugins (like Akka.Cluster.Tools).
hah! lol. Woops. Well feel free to do a PR ? :D
@denisobm I had problems with Akka.Cluster.Tools and Wire 0.7.1 (see issue #2365 ). With Akka.NET 1.1.3 I hoped together with Hyperion this should be fixed but I am getting Cannot find serializer with id [-5] error with just getting the pubsub mediator without using it. So not sure if going Hyperion is already an option. Still investigating this issue.
Ah, the serializer error was caused by really one node still using wire. fixed that but getting some disassociation problems with one node, still investigating.
What is the best method to guarantee there is one instance of an Actor per cluster node (is it using an ActorSystem extension?)
@DamianReeves may be consistent-hashing-router will suit your needs
I think that would require me to know how many nodes would be in my cluster (we can dynamically add worker nodes in our system)
@DamianReeves per node or per cluster?
per node - we usually do that through actor system extensions. Most of them have their custom actors (often 1 per node) attached. But this can be generalized to creating actor directly under the supervision of root actor (either /user or /system).
per cluster - cluster sharding, but you probably know about that
Hello, I just would like to know if akka .net actors could communicate remotely with akka actors running on a JVM ? Thanks.
Must be .NET to .NET to serialise/deserialise. All you could do is introduce a non-Akka channel and independent data format.
How can an actor get its Akka.Remote hostname which is configured in akka.hocon? Self.Path.Address.Host is empty for local actors...
I'm building a multitenanted Akka app. In that app I'm using EventStream for local pub/sub. Since it's multitenanted, I wonder if it's a good idea to have separate EventStream per tenant (and not using the ActorSystem's EventStream). Tried, technically it's working, just wonder if I am overlooking any possible issues going down this path.
@ZoolWay One way would be to read directly from the config.
Hm, ok, I am checking how far I can go using Context.System.Settings.Config.GetString("akka.remote.helios.tcp.hostname")