akkadotnet/akka.net

Port of Akka actors for .NET

Aaron Stannard

@Aaronontheweb

I haven't followed the earlier thread

Bart de Boer

@boekabart

TLDR: snapshot table is empty, however, I get a snapshotOffer about 50% of startups, with the most recent Journal entry as the data source (time, seq Nr, type, data)

Aaron Stannard

@Aaronontheweb

LOL

oh man

Bart de Boer

@boekabart

well this is production code at a customer, so, less LOL than you'd imagine.

(when we get the snapshot offer, there are no journal recovery msgs)

Aaron Stannard

@Aaronontheweb

in terms of the Postgres HOCON

what are the table names being used?

Bart de Boer

@boekabart

default

snapshot_store and event_journal

Aaron Stannard

@Aaronontheweb

I wonder if the issue is the metadata table

but that's very odd

and also, a reason why we need akkadotnet/akka.net#3811 back

this crap would immediately power vomit an exception since the snapshot store couldn't deserialize those events

rather than YOLO serialization, which allows this type of error to silently fail in the background without any clear explanation

/ rant off

Bart de Boer

@boekabart

metadata table is empty btw

Aaron Stannard

@Aaronontheweb

can't be that then

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?

Bart de Boer

@boekabart

postgres project?

Aaron Stannard

@Aaronontheweb

correct

Bart de Boer

@boekabart

check

Aaron Stannard

@Aaronontheweb

since it seems to be specific to the Postgres driver

Bart de Boer

@boekabart

I see nothing weird in the postgres code though

Aaron Stannard

@Aaronontheweb

could be an issue with Akka.Persistence.Sql.Common

so maybe log an issue on the main Akka.NET project isntead

Bart de Boer

@boekabart

Except the postgres is on 1.3.9 but that shouldn't be an issue

Aaron Stannard

@Aaronontheweb

that will get more visibility at least

Bart de Boer

@boekabart

Will do

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

Aaron Stannard

@Aaronontheweb

well, we did make some important fixes to Akka.Persistence.Sql common in 1.3.12, 1.3.13, and 1.3.14

none for what you're describing really

serialization fixes and bug fixes for the CircuitBreaker

Bart de Boer

@boekabart

The app is using 1.3.14

Aaron Stannard

@Aaronontheweb

the plugin might need to be upgraded

Bart de Boer

@boekabart

ah, but maybe not common 1.3.14, let me check

Aaron Stannard

@Aaronontheweb

it definitely needs to be upgraded for the serialization fixes

which affected things like Cluster.Sharding

Bart de Boer

@boekabart

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    |

Aaron Stannard

@Aaronontheweb

nice

been meaning to add something like that to Petabridge.Cmd

Bart de Boer

@boekabart

But I don't think that means a rebuild/fix to PostgreSql would be needed right?

Btw we switched to Sqlite for a while, which works 100% ok

Hmm, could AkkaNetContrib/Akka.Persistence.PostgreSql#65 be related?

Aaron Stannard

@Aaronontheweb

yeah, that looks exactly right

Bart de Boer

@boekabart

I'm writing a fresh one in that project now, maybe if indeed it turns out related, they can be linked.

Aaron Stannard

@Aaronontheweb

sounds good

but what you're describing sounds like that type of side effect

Where communities thrive

People

Repo info

Activity