AsyncBehavior got dropped a long time ago, only
Suspend is supported now, there is an overload of Receive that accepts a Func<T, Task> it have been renamed to ReceiveAsync in 1.0.7
For a monitoring solution for our services (not using clustering), what would be the best way to present a "list/tree" of actors of a local actorsystem. Having each actor respond to a "getchildren" message or is there a way to ask the actorsystem this? Is there a way to traverse the actor tree?
Hi, AroundReceive for UntypedActor allways returns true and ReceiveActor inherites from UntypedActor without changing this behavior. Shouldn't ReceiveActor return false for AroundReceive if for some reason the message wasn't handled by a Receive function defined in a ReceiveActor?
The actor in there illustrates a way you can "explore" your actorsystem.
However once again. this is not officially supported stuff. But it should give you a nice sample on how you can do this.
basically what it boils down to is you recursively apply an Identify message on an ActorSelection with wildcard
Problem is, you never know when you are done. So running this could kill your cluster :P because you;d end up continually spamming it with identify messages.
But it you could tweak it with clear end-conditions, or be able to restrict it parts of your cluster only. It could be the basis of a nice tool.
could you set that as an issue on github?
@eyantiful since you can send message through cluster in multiple ways, you need to be more precise. There are few various examples here i.e. cluster section from core repo and cluster web crawler
@Horusiath sorry for the minimalism.
I have a custom serializer (ProtoBuf.Net) for type Message.
Message has (among others) IActorRef property for the initiator actor.
In the samples you mentioned the default serializer is used as far as i can tell.
Might be ISurrogated interface which should be surrogated?
I guess the question is more is passing IActorRef around good practice?
In a low-latency application what is the overhead of the resolving for each message?
I have a custom serializer (ProtoBuf.Net) for type Message.
Message has (among others) IActorRef property for the initiator actor.
In the samples you mentioned the default serializer is used as far as i can tell.
Might be ISurrogated interface which should be surrogated?
I guess the question is more is passing IActorRef around good practice?
In a low-latency application what is the overhead of the resolving for each message?
@ArturKarbone Not sure if this is production ready, but I think you are looking for https://github.com/akkadotnet/Akka.Quartz.Actor cc @maxim-s
passing IActorRef is good, if used when necessary. Also how low-latency do you mean?
We are working on increasing the performance of Akka.Remote in v1.5
@JeffCyr Im currently POC to see how far can we go with minimum nodes in order to asses cluster size...
On v1.5 we were at 100K msg/sec for the same test, and there were still room for improvements
also for communication between nodes, take a look at Wire - it supports everything, default akka serializer should support and has quite good performance - you can see some comparison here
I get exception while executing TakeSnapshot command for persistence actors implemented in F#:
"Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'."
System.InvalidCastException: Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'.
at Akka.Persistence.FSharp.FunPersistentActor`3.OnCommand(Object msg)
at Akka.Persistence.UntypedPersistentActor.ReceiveCommand(Object message)
at Akka.Persistence.UntypedPersistentActor.Receive(Object message)
at Akka.Actor.ActorBase.AroundReceive(Receive receive, Object message)
at Akka.Persistence.Eventsourced.<ProcessingCommands>b__90_0(Receive receive, Object message)
at Akka.Persistence.Eventsourced.AroundReceive(Receive receive, Object message)
at Akka.Actor.ActorCell.ReceiveMessage(Object message)
at Akka.Actor.ActorCell.Invoke(Envelope envelope)
"Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'."
System.InvalidCastException: Unable to cast object of type 'Akka.Serialization.WireSerializer' to type 'Akka.Serialization.NewtonSoftJsonSerializer'.
at Akka.Persistence.FSharp.FunPersistentActor`3.OnCommand(Object msg)
at Akka.Persistence.UntypedPersistentActor.ReceiveCommand(Object message)
at Akka.Persistence.UntypedPersistentActor.Receive(Object message)
at Akka.Actor.ActorBase.AroundReceive(Receive receive, Object message)
at Akka.Persistence.Eventsourced.<ProcessingCommands>b__90_0(Receive receive, Object message)
at Akka.Persistence.Eventsourced.AroundReceive(Receive receive, Object message)
at Akka.Actor.ActorCell.ReceiveMessage(Object message)
at Akka.Actor.ActorCell.Invoke(Envelope envelope)
I inspected Akka code and apparently this line fails:
let serializer = UntypedActor.Context.System.Serialization.FindSerializerForType typeof<obj> :?> Akka.Serialization.NewtonSoftJsonSerializer
let serializer = UntypedActor.Context.System.Serialization.FindSerializerForType typeof<obj> :?> Akka.Serialization.NewtonSoftJsonSerializer