first thing I'd look at is how the snapshot store is reading from the rows
because that's truly weird
can you file an issue on that project?
so maybe log an issue on the main Akka.NET project isntead
I tried to add some
Console.Writeline to the postgres code but after building, I couldn't get that dll to work with the rest
dotnet version issues I guess
none for what you're describing really
serialization fixes and bug fixes for the
CircuitBreaker
which affected things like Cluster.Sharding
Gotta love good logging:
| Assembly (N=189) | Version |
|------------------------------------------------------------+-------------|
| Akka | 1.3.14.0 |
| Akka.Logger.log4net | 1.3.1.0 |
| Akka.Persistence | 1.3.14.0 |
| Akka.Persistence.PostgreSql | 1.3.9.0 |
| Akka.Persistence.Sql.Common | 1.3.14.0 |
| Akka.Persistence.Sqlite | 1.3.14.0 |
been meaning to add something like that to Petabridge.Cmd
Hmm, could AkkaNetContrib/Akka.Persistence.PostgreSql#65 be related?
but what you're describing sounds like that type of side effect
@Aaronontheweb @Horusiath I found a clear correlation between smth in the logging, and the recovery leading to a phantom SnapshotOffer.
In all the BAD cases, these two lines are immediately followed by the Snapshot offer
In all the BAD cases, these two lines are immediately followed by the Snapshot offer
akka.persistence.journal.postgresql] Started (Akka.Persistence.PostgreSql.Journal.PostgreSqlJournal)
akka.persistence.snapshot-store.postgresql] Started (Akka.Persistence.PostgreSql.Snapshot.PostgreSqlSnapshotStore)
and only after THAT, the
ReplayFilter creation is logged:[akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql/$a] Started (Akka.Persistence.Journal.ReplayFilter)
[akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql] now supervising akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql/$a
we're going to replace the built-in HOCON with the external library lock stock and barrel
in all the GOOD cases, the order is the other way around:
[akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql] Started (Akka.Persistence.PostgreSql.Journal.PostgreSqlJournal)
[akka://TitleCatalogizerPPTEST/system/akka.persistence.snapshot-store.postgresql] Started (Akka.Persistence.PostgreSql.Snapshot.PostgreSqlSnapshotStore)
[akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql/$a] Started (Akka.Persistence.Journal.ReplayFilter)
[akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql] now supervising akka://TitleCatalogizerPPTEST/system/akka.persistence.journal.postgresql/$a
[[akka://TitleCatalogizerPPTEST/user/TitleCatalogizer/Queue/RuntimeActor#384178050]] Recovering an expected Divv.XiXi.TitleCatalogizer.Actors.Runtime.RuntimeActor+EnqueuedWorkI've just done this 15 times, and it's true for all 7 failing and all 8 OK cases.
So there seems to be some kind of race
After some years as an akka.net user, I want to make a more deep dive into the framework.
For this reason, I checked out the actual source code (dev branch) and stared a build and unit testing (like descriped here). But I got in trouble with the existing unit tests. I can't run all tests successful. I have 3 of 4195 unsuccessful tests:
For this reason, I checked out the actual source code (dev branch) and stared a build and unit testing (like descriped here). But I got in trouble with the existing unit tests. I can't run all tests successful. I have 3 of 4195 unsuccessful tests:
Akka.MultiNodeTestRunner.Shared.Tests.ParsingSpec.MessageSink_should_parse_Runner_log_message_correctlyAkka.MultiNodeTestRunner.Shared.Tests.ParsingSpec.MessageSink_should_be_able_to_infer_message_typeAkka.MultiNodeTestRunner.Shared.Tests.Persistence.JsonPersistentTestRunStoreSpec.Should_load_saved_JSON_TestRunTree
I have no code changes, its the originaldevbranch.
Is this normal, or did I something wrong?
@boekabart I'm afraid I'd need a reproducible use case to understand what's happening
