These are chat archives for akkadotnet/akka.net
I am hoping for some help and understanding.
I am just starting to a development effort with Akka.net and clusters.
While I have not used clusters or Akka before, I have developed distributed systems.
I have found that logs are one of the most important piece of information to help in diagnosing when a system mis-behaves. This is especially true for systems at a customer's site or internally if it's not being monitor all the time. With this in mind, I wanted to consolidate logs. I can't see how to configure the system to consolidate logs into 1 (or a few places). My initial thoughts would be to have all seed nodes to have a full copy of the logs. This would be the permute place for logs, but I could see other actors wanting to also monitoring all logs for analysis and/or GUI type of needs.
My question is has anybody done this, what are the best practices for logging in a cluster and do I need to develop my own logging actors to get this kind of behavior?
Also as a side question, what are the best practices for handling clock differences between nodes in a cluster. This is especially true for logs to help in knowing what has happened when compared to other nodes.
AtLeastOnceDeliveryActorbehave if their underlying database becomes unavailable?
GetRouteesmessage to the router
Poolrouter, you'll get a list of
Routeeslist for any routee that isn't equal to yourself
how do PersistentActor and AtLeastOnceDeliveryActor behave if their underlying database becomes unavailable?
@Aaronontheweb if this problem occurs, Journal will send a message about failure back to the persistent actor:
PersistenceFailurewith details for each event, that could not be stored
RecoveryFailure(exception)(you can also override
OnReplayFailuremethod which unwraps message retrieval)