@defrag2_twitter As long as it's idempotent and won't fail (in your example it's get-or-create an actor), it should be good to go
however, I could have a persistent actor registering "login" events for each shop, so this way I could tell which shops are available to order from
i have a question... i can'T seem to get akka testing to run wiht nunit 3 (any version). i seen there were some fixes done around an issue regarding nunit3... but i can't seem to make it work. anyone got any clues?
Hey guys, I'm scaling my application with cluster sharding, and have a look at multinode test kit (http://getakka.net/articles/networking/multi-node-test-kit.html). How it supposed to be debugged? is there any guide? may be runners for Resharper Tests, as for NBench ? (https://github.com/Pro-Coded/Pro.NBench.xUnit) I can imaging only attach VS to multinode test runner, and it seems to be painful and long process. (
@andreyleskov debugging MNTR specs is a dark art
having done it for years, I have a couple of approaches I use
first - relying on logging as your primary source of information is the lowest-friction path
trying to debug 4-5 processes running concurrently
is going to end poorly usually
especially if you don't know where the problem is
is a free add-on to Visual Studio
zero clue if that supports .NET Core or not
that can help get the debugger attached to breakpoints in the child process
so my methodology is this: use logging to smoke out the error
the MNTR runner will produce detailed logs for each node
get enough log data to form a theory as to why the thing might be failing
conditional break points are you best friend here too, btw
should only start firing once you're close to the error condition
multi-node tests, by their very nature, are big and cumbersome
but they're the most reliable way to put real-world theories around handling things like failover, network issues, etc, to the test
I have a failover scenario where a cluster singleton has to migrate from one node to another
I'm going to be using the MNTR to test my recovery mechanism there
because a simple unit test can't do it justic3e
have a similar scenario where the node with the singelton running on it gets blacked out temporarily and comes back
"does my cluster react according to my plan?" is what my MNTR spec tries to answer there
by the way - is there any good profiling tool for akka.net like dotTrace? I'm using NBench to measure performance and looking for a simpler ways to find bottlenecks
or any guide how to analyze akka-based application performance with common tools
best practices, may be
@thomaslazar please provide a minimal example for reproducing the issue
but it's in early stages still
Hi @Aaronontheweb
In your post here: https://petabridge.com/blog/intro-to-persistent-actors/ , you mentioned the following:
The PersistenceId and the SequenceNr, together, form the primary key. And the sequence number is a value that monotonically increases in-memory inside the persistent actor - so imagine if you have two actors with the same PersistenceId but different sequence numbers writing to the same store. It will be chaos and will inevitably error out - so that’s why it’s crucial that every PersistenceId be globally unique within your ActorSystem (at least for all actors writing to that store.)
I have a question regarding the "PersistenceId" in Akka.net in a cluster. Does it work like this or should I need a specifier per node ?