These are chat archives for akkadotnet/akka.net
Hmm, I am wondering. Scenario is cluster but could be remote as well. Why do I need an actual type of an actual if that Actor is need deployed locally? I am creating the router to some remote actors like this:
var props = Props.Create<DummyActor>().WithRouter(FromConfig.Instance); var ref = this.actorSystem.ActorOf(props, name);
Sure thing is that
DummyActor here does not matter because on the remote nodes there will be another type used for that referenced actor. So why do I require it at all?
Props.Emptyif I remember correctly, but haven't used it in such scenario
DummyActorwill be used but that would not be a valid scenario in my case.
What would be the cause or is this normal that I get a DeathWatchNotification as a DeadLetter for each Actor that my router created.
So if I have tallyRouter actor configured for nr-of-instances = 100 I get 100 DeathWatchNotification which increases counter.
I need to explain to someone who might be looking at the counters and why I have thousands and thousands of them.
It appears to happen after I get the <Terminate> message which I should as I do a Context.Stop(tallyRouter).
Message: <DeathWatchNotification>: [akka://MyService/user/jobmaster/monkey/workercoordinator/tally/$h], ExistenceConfirmed=True, AddressTerminated=False
IActorRefto the actor you want to message directly into the event handler
ActorSystem.ActorOfare easily passable to external contexts