i will try to check internal logs
thanks for help though
@Shuffzord after running into a similar issue a couple months back, I concluded that nlog likes to fail silently when it can't parse its config file. I ended up hard-coding the following InternalLogger settings, so that it wouldn't be quite so silent:
public class Program
{
public static void Main(string[] args)
{
// Ensure NLog logs errors even if config file can't be parsed
InternalLogger.LogLevel = LogLevel.Error;
InternalLogger.LogToConsoleError = true;
InternalLogger.LogToTrace = true;
InternalLogger.LogFile = "nlog.errors";
// Initialize topshelf service
HostFactory.Run(x =>
{
x.SetServiceName("MyService");
x.SetDisplayName("My Service");
x.UseNLog();
x.StartAutomaticallyDelayed();
x.Service<MyService>();
});
}
}
Hi. I have a quick question. On the akka-bootcamp repo, it mentions that the support for F# is accepted. What's currently lacking with the F# implementation compared to the C# one ? I'd like to be able to implement an event-based architecture with Akka.NET to create an rpg prototype. Am I getting over my head here doing it with F# ?
@Kavignon default F# API doesn't allow you to describe some things that are necessary for features like cluster sharding or cluster singleton (Akkling API does however) - in general F# API is less used and less tested and you'll have less examples for it - usual thing in smaller communities.
some of our other plugins use JSON for persistence
I think the Sqlite one does
am I right about that @alexvaluyskiy ?
cool. Is this something the user has to remember or can the persistence plugin enlist the correct serializer.
Meaning if change my serializer to wire and then I switch my persistence plugin to one requiring JSON, can I ensure I don't get wire formatted chunks sent to the persistence writer?
akka.actor {
serializers {
redis = "Akka.Serialization.YourOwnSerializer, YourOwnSerializer"
}
serialization-bindings {
"Akka.Persistence.Redis.Journal.JournalEntry, Akka.Persistence.Redis" = redis
"Akka.Persistence.Redis.Snapshot.SnapshotEntry, Akka.Persistence.Redis" = redis
}
}
For example I'm processing a file. I might have many actors operating in parallel doing different things but all at the same time and I want to send a notification to a user's email address when I'm finished with all of the sub processes involved in processing the file.
I'm trying to figure out how to coordinate signaling that ALL of the actors involved have finished their part of the processing
@ronnieoverby IMHO the actor models's way of achieving this is to implement the actor that needs to dispatch many parallel tasks and collect its results as a reactive accumulator: it sends messages to all worker actors at once and falls asleep. The worker actors sends back its results which are being accumulated by the dispatcher.
There is also a great post by @Horusiath on the philosophy of Akka: http://bartoszsypytkowski.com/dont-ask-tell-2/
I am trying to play around with EventsByTag in Akka Persistence but running into an issue. I have defined config:
// In config
event-adapters = {
security-tagger = "AkkaPersistenceTest.SecurityTagger, AkkaPersistenceTest"
}
event-adapter-bindings = {
"AkkaPersistenceTest.SecurityEntity, AkkaPersistenceTest" = security-tagger
}
public class SecurityEntity
{
public Guid Id { get; set; }
public string Name { get; set; }
public string Identifier { get; set; }
}
public class SecurityTagger : IWriteEventAdapter
{
public SecurityTagger(ExtendedActorSystem system) // For some reason it actually wants a constructor with actor system.
{
}
public string Manifest(object evt)
{
return "";
}
public object ToJournal(object evt)
{
var e = evt as SecurityEntity;
if (e == null) return evt;
Console.WriteLine("Tagging security {0} with {1}", e.Id, e.Identifier);
return new Tagged(e, new[] { e.Identifier });
}I see it instantiate the Tagger but never calls the ToJournal and never records the actual tags on the persistence entry. I am using Akka.Persistence.Cassandra plugin based on the PR submitted by Constantin. Am I missing some configuration? I see the actual persistence working and event recorded, just without the tags. Thanks.
@Aaronontheweb interesting writeup of DigiOutsource. I noticed they're planning to use Service Fabric -- is there any documentation of how they will be setting this up? A (semi-) official starter solution demonstrating a basic 5 node akka.net cluster bootstrapped from Service Fabric would be very useful.
I think I'm just going to bite the bullet and do something myself on SF soon
awesome... it's something I've been meaning to play around with myself, but other priorities always get in the way (geez... the business actually wants new features and bugs fixed?!?). And getting started using something from the Powers That Be™ that has proven itself in a production scenario would likely save hitting a lot of pitfalls along the way.
that will be a great feature. @Horusiath do you have a recommendation for what persistence plugin is the best starting point for a new persistence plugin writer; I've been splitting between looking at MongoDb, Redis, and the EventStore plugin located here: https://github.com/vladkosarev/Akka.Persistence.EventStore
I would thing EventStore has more in common with Marten since they both natively implement event sourcing
But the EventStore plugin is 7 months old
If I want to determine if a given entity already exists in the system using a given tag for it, is using EventsByTag stream an appropriate way to do so? Is there some sort of marker that tells me that there are no events and that means this entity doesn't exist, and reading one event would give me the latest event info that has been processed? Thanks.
@mmisztal1980 yep
that's how you cancel them
what's up with Mono by the way?
http://petabridge-ci.cloudapp.net/viewLog.html?buildId=15948&tab=buildResultsDiv&buildTypeId=AkkaNet_LinuxMonoBuild&guest=1 - super close to having it pass the entire test suite
8 tests shy
E
lol