does anybody knows the way this worked? maybe an marker interface for the messag?
so as a new feature... does it make sense to support a marker interface for messages which doesn't influence the idle timeout of the actor which was set via "Context.SetReceiveTimeout()" ?
I am thinking about management messages like "GetStatistics". If an actor recieves that message he can answer that but it should not extend the idle timeout for passivate the actor
I use this "RecieveTimout" message to passivate the actor
now if I send only a management message to the actor I dont want it to extend the "RecieveTimeout" timespan.
if the actor can passivate it will, if not it will ignore the shutdown and receivetimeout
even if u ignore on command like GetStatistics for the receivetimeout, the sender of GetStatistics dont know if its alive or not, the coordinator would need to reply or start the actor
actor A
coordinator C
Scenario 1
- A sets RecieveTimout(5 min)
- A recieves no message in time
- after 5 min scheduler send A "RecieveTimout" message
- A sends "Passivate" message to coordinator
- ...passivating is going on
Scenario 2
- A sets RecieveTimout(5 min)
- A has nothing to do for 4 min
- A recieves a "management" message (should not influence RecieveTimout but now scheduler will extend RecieveTimout to 5 min again)
- Passivating will be postponed to further 5 min -> Scenario 2 restarts
in scenario the passivating of the actor is postponed because there a unimportant management message
but i would even make on ReceiveTimeout: Self.Tell(Shutdown.Instance)
On Shutdown: if(CanPassivate) Passivate()
and when to increase the "retirement" counter? on each important message?
but i am not there jet by myself
i am getting them in burts
and often delayed
is there a way to specify all actors below users with all children?
and subchildren and grandchildren and so on ....
Hello, now with deprecation of PersistentViews I am a bit lost about capabilities to monitor state changes of persistent actors. We want to build a Web site that visualizes both journals and snapshots, i.e. it will display the flow of state changes across all actors (possibly also state snapshots). I've found a few examples using SingalR but they were limited to receiving events for some specific actors. But is there a way to receive system-wide state changes for persistent actors?
@object persistent views will be obsoleted in the favor of akka.persistence.query, which will allow to build streams on top of event journals - depending on the journal, you will be able to track mulitple different persistence ids with it
Akka.Cluster.Tools question.
I am doing the following and I expect that if I kill off the remote actor that it would trigger the Terminated message but it does not seem to be doing that.
I am doing the following and I expect that if I kill off the remote actor that it would trigger the Terminated message but it does not seem to be doing that.
Receive<ClusterManager.SubscribeToManager>(ic =>
{
Program.MyActorSystem.Settings.InjectTopLevelFallback(ClusterClientReceptionist.DefaultConfig());
clusterClient = Program.MyActorSystem.ActorOf(ClusterClient.Props(ClusterClientSettings.Create(Program.MyActorSystem)));
Context.Watch(clusterClient);
clusterClient.Tell(new ClusterClient.Send(ActorPaths.ClusterManagerActor.Path, new ClusterManager.SubscribeToManager()));
});
Receive<Terminated>(ic =>
{
_logger.Info("Address Terminated: {0}", ic.AddressTerminated.ToString());
});
