because..:
beating protobuf when no version tolerance :D
Hi, I'm looking a bit on Akka.Cluster and see a lot of examples with routing. Is all communication with actors when using Akka.Cluster done through routing? I might have some actors that there should only be one of. How do I get a hold of that one? I've been looking around the WebCrawler sample and I see a lot of routers...
Despite that bug though, Akka.Monitoring working out well for you?
if you're participating in the Akka.Cluster contributor's meetings, we're starting now - if you had no idea this was going on and want to start contributing going forward, jump on in here https://plus.google.com/hangouts/_/ytl/sSPRzi9D_lWeJgtaM57TzySeAJ-lKVqFEZf-Iu_Nh8g=
finished our Akka.Cluster contributor's meeting - we did a pretty job documenting and exploring how the multi-node test runner actually works. If you folks are interested in working on Akka.Remote, Akka.Cluster, Cluster.Sharding, etc... this is good stuff to know: https://www.youtube.com/watch?v=xwmHWnIUmTY
btw. since event adapter stuff is done, I want to standarize SQL-based journals a little (Akka.Persistence.Sql.Common) and add a querying capabilities to them (my proof of concept branch)
each of the Akka.Persistence implementations gets a nightly integration test anytime our dev branch changes
where we automatically upgrade them to the latest version of Akka.NET
because right now I don't have any way of having those integration builds "push" their results out to any external service yet
might have them send an email to a mailing list or post a Github issue
just saw one of these
Google.ProtocolBuffers.UninitializedMessageException get thrown when the NodeTestRunner was booting up
happened inside the plumbing of the
TestConductor
the error has a pretty specific meaning - a Protobuf was missing a required field: https://developers.google.com/protocol-buffers/docs/reference/java/com/google/protobuf/UninitializedMessageException
I'm going to poke around and debug this and see if I can isolate the issue
my lord and saviour for multi-node test debugging: http://blogs.msdn.com/b/visualstudioalm/archive/2014/11/24/introducing-the-child-process-debugging-power-tool.aspx
@bobbychopra in terms of measuring the throughput of an actor, you can use this to instrument the
Receive method: https://github.com/petabridge/akka-monitoring
supports AppInsights, StatsD, and now performance counters
as for measuring the queue length of the mailbox - unfortunately there isn't a public API to access that :\
we'll be working on that when we do a more "holistic" solution for integrating monitoring directly into Akka.NET core
essentially we're going to have an engine in place, not too different from our logging engine, which will expose metrics and drains for collecting those sorts of metrics
that's a way's out for the time being though - no plans to start on that until some other big pieces of infrastructure (i.e. Akka.Cluster, TLS) are finished
Hey all, For long lived/single instance dependencies (in my case neo4jclient) what is the appropriate pattern for passing that dependency to an actor? Pass the instance to the constructor or factory method for use in PreRestart? Should PostRestart be overridden as not to call PreRestart again? I'm sure i found some succinct doco/examples somewhere, but for the life of me I can't find it. Many thanks!
@rogeralsing I know that you're working on Wire for fun / proof of concept - but I think, it's a good moment to talk with Typesafe guys about common way of message serialization between JVM/.NET specifically for the akka needs. I know that they have hard time using default Java serializer too.
hopefully usefull to people.