Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 14:20
    Aaronontheweb commented #4092
  • 14:14
    Aaronontheweb labeled #4089
  • 14:14
    Aaronontheweb labeled #4089
  • 14:11
    Aaronontheweb synchronize #4089
  • 14:10
    Aaronontheweb synchronize #4086
  • 14:09

    Aaronontheweb on dev

    Convert to ImmutableHashSet for… (compare)

  • 14:09
    Aaronontheweb closed #4090
  • 12:04
    nagytech synchronize #4092
  • 11:53
    nagytech synchronize #4092
  • 11:49
    nagytech edited #4092
  • 11:40
    nagytech opened #4092
  • 11:32
    nagytech edited #4091
  • 11:32
    nagytech opened #4091
  • 10:13
    nagytech commented #3954
  • 05:29
    nagytech commented #4090
  • 05:29
    nagytech opened #4090
  • Dec 11 23:52
    scptre commented #4082
  • Dec 11 14:26
    nagytech commented #3954
  • Dec 11 11:18
    nagytech edited #4089
  • Dec 11 11:17
    nagytech opened #4089
Zetanova
@Zetanova
sql-server for now. but the storage type should be picked by the AR-type
Christian Duhard
@cduhard
how do you mean?
Zetanova
@Zetanova
file, document-store, sql are all valid
Christian Duhard
@cduhard
i was going to give EventStore a try
Zetanova
@Zetanova
File => for very large AR's maybe explicit on a partition/drive SSD
DocumentStore => normal for AR's
sql => maybe faster for some kind of operations (need to test later on)
Christian Duhard
@cduhard
weird getting dead letters now
Zetanova
@Zetanova
In a local akka.net buget build where to set the BUILD_NUMBER of a package? Want to patch the Akka.Persistence.Sql.Common so that the SqlServer is dont updating it on install
Zetanova
@Zetanova
RELEASE_NOTES.md file.
Christian Duhard
@cduhard
wonder why EventStore ain't got no love for a Akka.Persistence
Yin Zhang
@melcloud
Dear all,
just wondering if it is safe to use PersistView?
My idea is to have an actor which persist events such as quoteCreated. Then once another service is online, a persistView actor is created and do at least once delivery to that service
Zetanova
@Zetanova
@Horusiath You already change in Akka.Persistence.Sql.Common the DbConnection to short use pattern?
Bartosz Sypytkowski
@Horusiath
@rogeralsing I think, we still have some problems concerning stashing and message duplicates - we changed custom equality to reference equality to detect duplicates inside the stash, but actually sometimes we may want to store the same message twice (like in the case of singleton messages or strings)
@Zetanova what do you mean?
Zetanova
@Zetanova
@Horusiath currently in JournalDbEngine and DbSnapshotStore the dbconnection is a singleton but executes concurrent sqlCommands on it (at least it is trying to do). the dbConnection should be create for each execution and disposed after. It is backed by the sql-connection-pool
Bartosz Sypytkowski
@Horusiath
this part is covered by #1306 - it will use new connection for each operation
Zetanova
@Zetanova
its not realy using a new connection, its peeking one from the sql-connection-pool
Bartosz Sypytkowski
@Horusiath
yes, I know ;)
Aaron Stannard
@Aaronontheweb
@stefansedich working on upgrading the version of Mono on our build agents
since the DNS system still barfs up those DNS assertions whenever I use NuGet.exe
Bartosz Sypytkowski
@Horusiath
when I said new connection, I meant new instance of DbConnection
Aaron Stannard
@Aaronontheweb
switching to the alpha channel I think
Zetanova
@Zetanova
@Horusiath the SnapshotStore is implemented as an actor and can use the singleton dbconnection and LinkList. Why not implement JournalDbEngine like this too? And maybe both .WithRouter()
Bartosz Sypytkowski
@Horusiath
@Zetanova SnapshotStore now will use dbconnection per request to. Also I'm concerned, that routers will affect reliability of message ordering
Zetanova
@Zetanova
@Horusiath even with this Hash-Router?
Bartosz Sypytkowski
@Horusiath
and since we already use async ADO.NET API for database communication I'm not so sure if spawning more journals/snapshot stores will be much help - but this could be measured
Zetanova
@Zetanova
I am not so sure that if the JournalEntires are processed in parallel, that they will be on disk in serial, most likly overlapped with the SeqNr.
of course in sql u can sort by SeqNr. on a FileStorage its maybe a bug
Bartosz Sypytkowski
@Horusiath
seqnr is generated by persistent actor itself
Zetanova
@Zetanova
yes but not saved
the JournalEntries are processed in batch
if one batch gets SeqNr 1-10 and the second batch 11-20
then it will land on disk most likly overlapped
1,2,3,4,5,6,11,7,8,12,8,13,14,9,15,10,16,17,18,19,20
Bartosz Sypytkowski
@Horusiath
AFAIK we use file storage only for snapshots right now - and it's highly not recommended to use it for anything else than tests
Zetanova
@Zetanova
and what are EventStorageEngines are doing with this seq. ?
ordering in memory and saving them or replying them 1:1 later?
Aaron Stannard
@Aaronontheweb
@stefansedich nope, we're still screwed: https://bugzilla.xamarin.com/show_bug.cgi?id=35509
Bartosz Sypytkowski
@Horusiath
sequenceNr is necessary to ordering events in scope of the persistent id used
Zetanova
@Zetanova
i dont not see your new code, but the current one from JournalDbEngine will overlap the batches
Bartosz Sypytkowski
@Horusiath
basically it's increased monotonically by the persistent actor (therefore there can be only 1 instance of it per persistent id at the moment) and saved with event. Once persistent actors recovers, the highest seqNr is retrieved from the journal before continuing any work
Aaron Stannard
@Aaronontheweb
working on compiling Mono from scratch now to see if that fixes it #yolo
Zetanova
@Zetanova
Is JournalDbEngine created for each PersistentActor?
Bartosz Sypytkowski
@Horusiath
This message was deleted
my bad, it's created once for whole journal
Zetanova
@Zetanova
yes
and even if