@langebo When working with actors it's best no to think in OOP terms. It's all about messages. When you build a state of AppointementActor from its events you are replaying messages that were received and persisted for the given AppointmentActor persistence ID. Events come from the event journal (event store). If AppointementActor state should include more than that (e.g. a number of ResourceActor events), then you have to arrange it yourself. This is why I'd go for storing all contained events under the same persistence ID (corresponding to the aggregate root, in your case it will be AppointmentActor).
hi all, I worked on an akka.net system 2 years ago but have nearly forgotten everything I learned. trying to get back up to speed but can't seem to find the really great article on the "work pulling pattern" that I had back then. Anybody know which one I might be referring to or where I can find something similar now? cheers
damn, thought it might be https://petabridge.com/blog/top-akkadotnet-design-patterns/
but we don't cover it there
@Aaronontheweb is there any documentation on how Lighthouse should be started and configured?
It seems like there's a lot of custom cases that aren't described anywhere (seed-node cycle, as I wrote in the previous message, and constant gateway association errors if lighthouse referenced by another lighthouse starts later than latter)
It seems like there's a lot of custom cases that aren't described anywhere (seed-node cycle, as I wrote in the previous message, and constant gateway association errors if lighthouse referenced by another lighthouse starts later than latter)
I'm using NLog to log errors in my akka app. I would like to be able to add additional data to the exception before it logs...including the message value. I was using PreRestart override for this which works, but I noticed the error often gets logged before that event is triggered so sometimes the extra data is not included. Where would be the appropriate place to do this kind of logging? Do I need a custom logger or some other approach?
@atresnjo take a look at actorselections and how addresses work: https://getakka.net/articles/concepts/addressing.html#querying-the-logical-actor-hierarchy
thanks tho
Is there any gotcha's when using Cluster Discovery Consul + Routing?
Here is my deployment config:
/other {
router = broadcast-group
routees.paths = ["/user/api"]
virtual-nodes-factor = 8
cluster {
enabled = on
max-nr-of-instances-per-node = 2
allow-local-routees = off
use-role = "other"
}
}I have the other console application running with an actor ready for messages at /user/api
Here is the cluster config:
cluster {
roles = ["other"]
}Logs are showing that the nodes are up and running with the correct roles.
But the when telling /user/other a message it keeps deadlettering. Anyway to debug what's going on?
Oh... I'm having no issues with routing when I'm broadcasting to the same role + enabling allow-local-routees. But once scaling up I'm sure the external routees wouldn't work :(
[ERROR][12/2/18 4:18:21 PM][Thread 0007][remoting] SkipLastField called on an end-group tag, indicating that the corresponding start-group was missing
Cause: Google.Protobuf.InvalidProtocolBufferException: SkipLastField called on an end-group tag, indicating that the corresponding start-group was missing
Cause: Google.Protobuf.InvalidProtocolBufferException: SkipLastField called on an end-group tag, indicating that the corresponding start-group was missing
Can my MsgPack serialization be the reason that message in protobuf is raised? All my own messages are serialized in MsgPack, but I can't find a lot googling this error.
Hello, can maybe someone Confirm that the first example releated to this: https://getakka.net/articles/intro/use-case-and-deployment-scenarios.html using FluentConfig is absolete and have to be updated ?
How can i configure hyperion serialization?
I followed getakka.net serialization document, but it doesn't work.
I followed getakka.net serialization document, but it doesn't work.
As you can see, matched serializer is still
NewtonSoftJsonSerializer
I've been using Akka.Net for over 3 years and just really enjoy working with Actors, messaging and SignalR.
Here is my latest creation - https://github.com/cgstevens/FileProcessor
Here is my latest creation - https://github.com/cgstevens/FileProcessor
and this can work simultaneously across multiple machines?
@Aaronontheweb Thanks Aaron!
Well I have only been working on my system but I did run a quick test and my work was in a different domain as well as a copy of my WindowsMonitor, so yes to answer your question :)
I am trying to get a project together that demonstrates all of the AWESOME tools you all have built.
So right now in the solution contains the following services:
Lighthouse - service discovery
Processor (EastCoast/WestCoast) - This is to simulate the Singleton Actor, there can only be one just like highlander :) Basically keeps track of jobs.
Worker (EastCoast/WestCoast) - This demonstrates the ClusterRouterPool and distributes the reading of a line.
WIndowsMonitor - WindowsForms application that allows you to view into the cluster... (just like my other I have created)
WebMonitor - This is using SignalR to funnel message from an actor which is using PubSub Mediator to subscribe to Topics from the Processor and Worker services.
Well I have only been working on my system but I did run a quick test and my work was in a different domain as well as a copy of my WindowsMonitor, so yes to answer your question :)
I am trying to get a project together that demonstrates all of the AWESOME tools you all have built.
So right now in the solution contains the following services:
Lighthouse - service discovery
Processor (EastCoast/WestCoast) - This is to simulate the Singleton Actor, there can only be one just like highlander :) Basically keeps track of jobs.
Worker (EastCoast/WestCoast) - This demonstrates the ClusterRouterPool and distributes the reading of a line.
WIndowsMonitor - WindowsForms application that allows you to view into the cluster... (just like my other I have created)
WebMonitor - This is using SignalR to funnel message from an actor which is using PubSub Mediator to subscribe to Topics from the Processor and Worker services.
@zimayel_gitlab yes, that's correct
we haven't supported that syntax in years
Hey guys,
I have data duplication issue when using TCP. I'm sending from "for" loop on client and reply with the same message from akka (echo).
If the message size 15 bytes + 4 for length, everything is perfect (sent 20k messages that is arrived in order and no duplication).
If message size more than that, duplications arrived. The pattern here is 1,2,3,4,2,3,4,5,6,7,8,2,3,4,5,6,7,8,9,10, ... (not always)
From my investigation the issue caused by
- <NetworkStream>.WriteAsync(packet, 0, packet.Length).ConfigureAwait(false) on client
or - <Tcp.Received>.Data.ToArray() on server (akka)
I have a repro project and will send to anyone who volunteers for investigation :)
@HIPERCUBE I've also captured traffic it shows that client sent 10 messages and got 22 in the reply https://drive.google.com/open?id=1KYSKINzPWPoyUuK5BWHR8PeXQPg7Z-iz
remark: this is a localhost
Phobos is a monitoring and tracing integration for Akka.Net build by @Aaronontheweb
the JVM has the advantage of using AOP like things to weave that stuff into your actors. .NET does not has that advantage
akka {
stdout-loglevel = DEBUG
loglevel = DEBUG
loggers=["Akka.Logger.Serilog.SerilogLogger, Akka.Logger.Serilog"]
log-config-on-start = on
actor {
provider = "cluster"
}
remote {
dot-netty.tcp {
hostname = "127.0.0.1"
port = 8081
maximum-frame-size = 256000b
}
}
cluster {
seed-nodes = ["akka.tcp://tradex@127.0.0.1:4053"] # address of seed node
roles = ["ordersync", "logger"] # roles this member is in
role.["ordersync"].min-nr-of-members = 3 # crawler role minimum node count
# auto downing is NOT safe for production deployments.
# you may want to use it during development, read more about it in the docs.
#
# auto-down-unreachable-after = 10s
}}