i will build a test solution and try if i get the same error there and if i do i'll up it on github
@Horusiath For the snapsot generation algo. there is beside event-count an other possibility. When each event has a timestamp and it is assumed that the application is pushing constantly events to the event-stream, then it is highly plausible that events in a short time frame are loaded faster then events over an longer timeframe. If the the events are over a long period >24h not snapshotted it can be done, even with only 2 events.
but as i said i'll try to make a test program that "hopefully" has the same problem
and one exception that gets passed back is a
TargetParameterCountException
and that doesn't work either
switching to wire in my testsolution fixed the problem.
and i am stoopid as usual. was all there. nice and clean in the log file... stuff just didn't got output to the stdout
Question: I've got a sharded entity actor. It creates a child actor to perform some duty. When this child gets stopped by the entity actor, the following log entry appears:
Akka.Actor.LocalActorRef: Message DeathWatchNotification from akka://bm2cluster/user/sharding/LoonbonVerwerking/3/d8c52c1e-4843-4092-9cc4-43ec8f774737/lbvverrijking to akka://bm2cluster/user/sharding/LoonbonVerwerking/3/d8c52c1e-4843-4092-9cc4-43ec8f774737/lbvverrijking was not delivered. 5 dead letters encountered.
Before implementing sharding, this message didn't get logged.. Any idea's?
@Aaronontheweb Thanks! I will take a look today. I got pulled off my project for a couple of months and now I am back on it.
I see I need to catch up on Cluster.Tools and the Persistence. I am still having cluster issues where if I deploy my Web Apps things get wonky...
Bad thing is that my web apps are my monitoring tools hence the reason for the need for Cluster Tools.
I see I need to catch up on Cluster.Tools and the Persistence. I am still having cluster issues where if I deploy my Web Apps things get wonky...
Bad thing is that my web apps are my monitoring tools hence the reason for the need for Cluster Tools.
Not sure if anyone goes to www.CodeStock.org in Knoxville but this July I submitted my 1 hour talk.
Plan on doing a similar talk like at the Akka.Net Virtual Meetup and now I want to dive deeper into the details about Akka.Net.
So if you want to take a minute and go vote that would be awesome and thank you!
http://my.codestock.org/#/app/sessionlisting/user/6477
Plan on doing a similar talk like at the Akka.Net Virtual Meetup and now I want to dive deeper into the details about Akka.Net.
So if you want to take a minute and go vote that would be awesome and thank you!
http://my.codestock.org/#/app/sessionlisting/user/6477
@Horusiath About the sharding persistence.. Can the journal and snapshot data be deleted at some point?
Can this be mitigated somehow?
@Aaronontheweb I just want to give a big thanks to whom ever did the Akka.Cluster.Tools!
Trying to monitor my cluster I had to be part of the cluster... and now I can get the cluster state and do commands to manage it without having to be part of the cluster.
My problem is when connecting to our Dev environment my tool or other nodes would freak out due to network packets dropping and just things start to become unreachable.
So moving the monitor to a website solved that issue except when my websites are unavailable... then what??
Once I have my internal tool working I will port it over to the Akka.Cluster.Monitor on github for anyone else to take advantage.
Trying to monitor my cluster I had to be part of the cluster... and now I can get the cluster state and do commands to manage it without having to be part of the cluster.
My problem is when connecting to our Dev environment my tool or other nodes would freak out due to network packets dropping and just things start to become unreachable.
So moving the monitor to a website solved that issue except when my websites are unavailable... then what??
Once I have my internal tool working I will port it over to the Akka.Cluster.Monitor on github for anyone else to take advantage.
'var messageId = Guid.NewGuid();
_topActors.System.ActorSelection("user/*").Tell(new Identify(messageId));
_topActors.System.ActorSelection("user/*").Tell(new Identify(messageId));
but how to collect the responses? there is only the "ResolveOne()" method. I also discovered the "Inbox" class but couldn't figure out to combine both
but i dont know it the "user/*" + identity is a good practice
The problem however is whenever I use real ActorRefs here, I get an exception about a loop: property Provider that's self-referencing.