Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 21:29
    Aaronontheweb commented #3863
  • 21:28
    Aaronontheweb synchronize #3863
  • 21:18
    Aaronontheweb synchronize #4000
  • 21:17
    Aaronontheweb commented #3964
  • 21:17
    Aaronontheweb commented #3964
  • 21:16
    Aaronontheweb synchronize #3964
  • 21:12
    Aaronontheweb commented #3964
  • 21:08
    Aaronontheweb synchronize #71
  • 21:04
    Aaronontheweb synchronize #3973
  • 21:00
    Aaronontheweb commented #71
  • 20:58

    Aaronontheweb on dev

    Akka.Persistence.TCK fix - chec… (compare)

  • 20:58
    Aaronontheweb closed #4002
  • 20:51
    Aaronontheweb synchronize #4002
  • 20:45
    Aaronontheweb commented #3811
  • 20:45
    Aaronontheweb commented #3811
  • 20:44
    Aaronontheweb labeled #4002
  • 20:43
    Aaronontheweb milestoned #4002
  • 20:43
    Aaronontheweb opened #4002
  • 20:37
    Aaronontheweb synchronize #71
  • 20:20
    Aaronontheweb synchronize #71
Zetanova
@Zetanova
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
Bartosz Sypytkowski
@Horusiath
with regard, that there's only one journal for each persistent backend
Zetanova
@Zetanova
if the PersistentActor is calling WriteMessages() with the first batch
sec
and who is calling WriteMessages() ?
Bartosz Sypytkowski
@Horusiath
journal itself
Zetanova
@Zetanova
parallel, most likly because i get this race conditions
it is fine until the batch of one PersitentActor are executed in parallel
and there should be a check in the Recovery Processdur
when the SeqNr > SnapshotNr+1 then RecoveryFailure
Bartosz Sypytkowski
@Horusiath
sorry, but I'm programming from like 15 hours now, but I seem to missed SnapshotNr somewhere in our discussion ;)
Zetanova
@Zetanova
I am allready missing Event-1 of an AR and get insatnly Event-2
SeqNr of the Snapshot
Bartosz Sypytkowski
@Horusiath
snapshot uses the same sequencer as journal, but it doesn't increment it
Zetanova
@Zetanova
If one Journal Event is missing in the recovery it should Fail
because of this bug, i have this state, not the AR is getting the second Event on recovery and missing the first one.
State of the AR can be then unlear and dangures
yes , i the same
did my TAX decalaration today at night
last minute
Bartosz Sypytkowski
@Horusiath
to make some quick summary: you've encountered moment, when you had sql journal storing in parallel events a-1 and a-2, but for some reason a-2 has been stored, while a-1 not, right?
Zetanova
@Zetanova
yes, because of the bug
it was now 4times
i am testing with 200 AR's
each gets a command and is persisting two events
(Created+Updated)
Zetanova
@Zetanova
I removed now the locks from the DBSnapotStore and getting again the Error at PendingOperations.Remove(tokenSource);
in the LoadAsync method
wahahahah
PipeTo is not waiting to complition
This message was deleted
Zetanova
@Zetanova
=> Concurrent execution in the Snapshot Actor
LoadAsync() => sawns a new thread (or takes one from the pool)
PipeTo is just execution on the same new thread and the end
if 10 messages are comming
then there will be lots of simultan executoon inside the actor