as you can see there, all of the NUKPGs I produced when I ran it yesterday definitely have binaries in them
based on the file sizes
ah, my bad!
those are the symbol pkgs
the true NuGet packages are screwed up
I can see that
so something must not have been updated in the FAKE script when paket was introduced
probably in the output copying step
let me check
@Zetanova that should work too
we use XUnit 2
I'm pretty sure that's been updated to work with the VS Test Runner
@Aaronontheweb with the hack about monitoring gossip and having the singleton live on the cluster lead, would this work if you had Lighthouse as your seed nodes?
you'd have to modify the source
couldn't use it OOB
it's definitely a hack
Cool, yeh just wanted to understand that - sounds like proper cluster singleton isn't too far away anyhow
fixed it @Horusiath
@Horusiath could you review #1455?
that should solve it
Thank you @Aaronontheweb for helping me
@Aaronontheweb still nothing
@Horusiath "System.TypeLoadException : Could not load type 'Akka.Actor.WithUnboundedStash' from assembly 'Akka, Version=0.8.0.0, Culture=neutral, PublicKeyToken=null'." whilst trying out the nuget packages for Akkling v0.2
you'll need newer version of Akka installed as set assembly bindings if needed
i am adding the 22.214.171.124-beta over nuget and no akka asm appears as reference
@Horusiath thanks, that got it. Odd that it would pull in such an old version.
I'm getting "has 0 routees" message with web-crawler sample
to link the local builded nuget packages, its the same behavior as with the prerelease, no akka assemblies are under references
@ramusbucket 0 routees means your cluster hasn't formed.
You should be able to work out what's going on via the console output
@thelegendofando thank you for your comments
It seems that I was ignorant about how to run those samples. The instructions given on Github wiki pages are not sufficient. I somehow figured out that I need to run "WebCrawler.CrawlService" and "WebCrawler.TrackingService" along with the "WebCrawler.Web" app and "Lighthouse" app
so I've just discovered that actors are created asynchronously (when ActorOf call completes my actor isn't guaranteed to have been ctor'd). Is there a way to control that, and also presumably if I send a message to an uncreated actor the message will be buffered untli it is created?
@ramusbucket if you run the solution it should fire up one of each service, although yes, you need a seed node, doesn't have to be Lighthouse.
@thelegendofando you are correct
What if I run those services from command prompt from Debug folder. No logs show up for lighthouse or crawler service
Hi! The simplest dummest question of the entire book I guess, but I have a use case where I have to correlate two message, but those message means data I cannot affort to loose. For this particular use case, one of the message knows (have and ID) the correlation with the second, but the second can be either never correlated with anyone, or correlated with one of the first one.
The first message is an actor how tries to reach the second if is available, second can arrive after first arrived, thus the first one is in charge of search for the second one. But actor for first need to be started even if a node crash. So my question is, how can achieve high availability on the even of a failure in one or more nodes in my cluster??
Thank you all in advance.
@Horusiath If I want to contribute in cluster tools and cluster sharding, where will be in the code a good start for reading and getting the sense of it?
@feanor41 your case can be solved by cluster sharding, but in general it's the case of some third service actor, that both actors use to establish the connection with each other
concerning Akka.Cluster.Tools and Akka.Cluster.Sharding - most (if not all) of the code is already ported, but I need to make multinode test runner specs working. If you want to help a little, I can try to find something, that could interest you. Just give me a while to reorganize the code ;)
@Horusiath Thanks, no rush. I was looking at Cluster Sharding documentation available and arrived myself to cluster sharding path. Thanks for confirm it.