These are chat archives for akkadotnet/akka.net

9th
Dec 2018
Onur Gumus
@OnurGumus
Dec 09 2018 08:32
@Horusiath , with akkling can we use object as the message type safely? Because doing so with persistent actor causes all messages such as ReplaySucceeded to come to actor as well. Perhaps the order should be changed for intercepting the messages.
Bartosz Sypytkowski
@Horusiath
Dec 09 2018 14:12
@OnurGumus yes, you can use IActorRef<obj>, but then you'll catch any obj matching signature, including system messages sent to an actor. There's no easy way to just filter them out. Once I'll be done with porting akka-typed, then this will be much easier and consistent to do.
Zetanova
@Zetanova
Dec 09 2018 14:26
hi, Why does the IPersistenceIdsQuery.PersistenceIds() not provide any filtering or offset logic? I cant find any other method to resume a query, beside the method with the EventsByTag + Offset. Is the regular why realy to save every LastSeqNr for each PeristenceId in a projection?
Bartosz Sypytkowski
@Horusiath
Dec 09 2018 15:28
@Zetanova if I remember correctly PeristenceIds only give you the list of PIDs known up until "now". If you're intersted with continuous stream of all new incoming PIDs, you can use AllPersistenceIds method.
Onur Gumus
@OnurGumus
Dec 09 2018 17:01
@Horusiath once I get the system messages, how can I return it back to system to be processed?
then first the message will be checked against system and if not object type will pick it up
ah of course then you can't access to the events even if you want to
Zetanova
@Zetanova
Dec 09 2018 18:44
@Horusiath Thx, for the advice, ther is a CurrentPersistenceIds and PersistenceIds method. But what i am interested in is to resume a stream (process restart) without the help of EventsByTag. If there are a lot of PID's (>100k) the readJournal.PersistenceIds is getting useless. What should a process do with the PId's without any metadata like timestamp, ordering-id? It can only load each individual stream on every process restart. That makes the method readJournal.PersistenceIds for larger event stores not very unperformant.
AndreSteenbergen
@AndreSteenbergen
Dec 09 2018 22:21
I have a question regarding the webcrawler example, when you have multiple apimasters and you set the routing algorithm to "router = consistent-hashing-group", would I really need to do a broadcast requesting if some other apimaster is already crawling that domain? Could I just simply check "Does this actor already have a crawler for domain XYZ"? The broadcast only really makes sense when it is round-robin instead of hashing? Or am I missing the point?