Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 18:58
    Aaronontheweb commented #3863
  • 18:16
    Aaronontheweb commented #4022
  • 17:52
    MaximG1234 commented #4054
  • 17:52
    MaximG1234 commented #4054
  • 17:52
    MaximG1234 commented #4054
  • 17:51
    MaximG1234 commented #4054
  • 17:49
    Aaronontheweb commented #4054
  • 17:49
    MaximG1234 commented #4054
  • 17:48
    MaximG1234 commented #4054
  • 17:47
    MaximG1234 commented #4054
  • 17:44
    Aaronontheweb commented #4054
  • 17:43
    MaximG1234 commented #4054
  • 17:42
    ismaelhamed synchronize #3863
  • 17:39
    MaximG1234 commented #4054
  • 17:35
    MaximG1234 commented #4054
  • 17:34
    MaximG1234 commented #4054
  • 17:31
    MaximG1234 commented #4054
  • 17:10
    Aaronontheweb commented #4054
  • 17:06
    MaximG1234 commented #4054
  • 17:05

    dependabot-preview[bot] on nuget

    (compare)

Peter Hvidgaard
@hvidgaard
ok, I'll try that.
Peter Hvidgaard
@hvidgaard
@Danthar I figured out what was wrong. I had an Actor that was a base for my other Actors that query a datastore. When creating a class it automatically creates the base class as well, leading to the issue. Nothing to do with SImple Injector.
Arjen Smits
@Danthar
ah, good to hear you figured it out. :+1:
Julien Adam
@julienadam
Hey guys, I have a cluster running with 6 nodes including 2 seeds (A and B), all started at the same time. According to the logs, the leader is trying to move seed node B to [Up] every 3 or 4 seconds. Node B appears as "Joining" to my monitoring node but never goes to the Up status. No dead letters, no exceptions. I've restarted the whole cluster twice but the situation persists. Any ideas ?
Bartosz Sypytkowski
@Horusiath
@julienadam does seeds know about each other? what if you'll introduce a little delay between starting them?
Julien Adam
@julienadam
all the nodes have both seeds set in the akka.cluster.seed-nodes config property. I'll try with a delay
interesting, it's always the last node I start that the leader is trying to move to Up but remains 'Joining' to the other nodes
Max
@maxpaj
Anyone got experience with Akka.Persistence with Redis storage connector? I can't get it to work and I'm getting no errors... It's weird.
Bartosz Sypytkowski
@Horusiath
@maxpaj how are you configuring it?
Max
@maxpaj
          persistence {
              journal {
                redis {
                  # qualified type name of the Redis persistence journal actor
                  class = "Akka.Persistence.Redis.Journal.RedisJournal, Akka.Persistence.Redis"

                  # connection string, as described here: https://github.com/StackExchange/StackExchange.Redis/blob/master/Docs/Configuration.md#basic-configuration-strings
                  configuration-string = "localhost:6380,ssl=false"

                  # dispatcher used to drive journal actor
                  plugin-dispatcher = "akka.actor.default-dispatcher"

                  #Redis journals key prefixes. Leave it for default or change it to appropriate value. WARNING: don't change it on production instances.
                  key-prefix = "akka:persistence:journal"
                }
              }

              snapshot-store {
                redis {
                  # qualified type name of the Redis persistence snapshot storage actor
                  class = "Akka.Persistence.Redis.Snapshot.RedisSnapshotStore, Akka.Persistence.Redis"

                  # connection string, as described here: https://github.com/StackExchange/StackExchange.Redis/blob/master/Docs/Configuration.md#basic-configuration-strings
                  configuration-string = "localhost:6380,ssl=false"

                  # dispatcher used to drive snapshot storage actor
                  plugin-dispatcher = "akka.actor.default-dispatcher"

                  #Redis storage key prefixes. Leave it for default or change it to appropriate value. WARNING: don't change it on production instances.
                  key-prefix = "akka:persistence:snapshots"
                }
              }
            }
Bartosz Sypytkowski
@Horusiath
it looks like you're not setting the plugin
if you want to use it as default
Max
@maxpaj
Oh okay, how do I do that?
Bartosz Sypytkowski
@Horusiath
akka.persistence.journal.plugin = "akka.persistence.journal.redis"
Max
@maxpaj
Oh... Right. Thank you!!
I was following this https://github.com/akkadotnet/Akka.Persistence.Redis - I guess it should say something there?
Bartosz Sypytkowski
@Horusiath
it's common for all persistence plugins, but you're right - it should be mentioned in readme
Max
@maxpaj
Alright! But how come it wasn't throwing any errors at me while my config was incorrect?
Bartosz Sypytkowski
@Horusiath
your config is correct (probably). It's just not used
Max
@maxpaj
Right, so it's using the default configuration for persistence then, which is what?
Bartosz Sypytkowski
@Horusiath
by default, journal is in-memory
Max
@maxpaj
Alright, how will that persist my events? Sorry, but this is strange to me... :'(
Bartosz Sypytkowski
@Horusiath
np ;) default journal stores all events directly in memory - it's not meant to be used for production, more for samples and testing purposes
so when your program stop, all events will perish
Max
@maxpaj
Alright, that makes sense :)
Aaron Stannard
@Aaronontheweb
@vladkosarev working on that today
@Horusiath Azure websites is fixed in dev
issue is that Azure websites doesn't support IPV6
Vlad Kosarev
@vladkosarev
@Aaronontheweb thanks, we reverted to 1.0.8
Aaron Stannard
@Aaronontheweb
yeah, sorry about that - trying to add support for IPV6 broke a ton of shit
growing pains there
although kind of surprised that so many parts of Azure don't support it - the thing has been out for like a decade
Aaron Stannard
@Aaronontheweb
@Danthar @Silv3rcircl3 working on updating our build script so I can make it mono-friendly
for all of the plugins
TL;DR;, in order for our Docker strategy to work with Akka.Persistence I basically need both parts of the testing process to run inside a Docker container
that will allow me to link the containers
today that looks like running everything on Mono for the testing stage
in the not too distant future, .NET Core
Aaron Stannard
@Aaronontheweb
@alexvaluyskiy @Silv3rcircl3 @Horusiath ready to merge I think: akkadotnet/akka.net#2294
that'll help me get the Mono suite passing
Bartosz Sypytkowski
@Horusiath
ok, I'm merging that
Aaron Stannard
@Aaronontheweb
just about have the PostgreSql test suite working on Mono
have to do a bunch of funky Linux-specific file globbing and crap
ty @Horusiath
Aaron Stannard
@Aaronontheweb
alright, I give up - between half the shit for Akka.Persistence.PostgreSql not working at all on Mono and Docker on Windows Server 2016 barfing up segfaults when I try to run postgres on it
I've exhausted the options for getting builds running for it again
right way to fix this is to force all Akka.Persistence plugins to work on Mono only for the time being (i.e. build chain, drivers work on Mono or no CI) - SQL Server, on the other hand, we should be able to get working on 2016
Aaron Stannard
@Aaronontheweb
alright, Mono build chain is able to run end to end except for some Akka.IO specs
more TCP stuff again
going to see if I can get some more information with the logging settings turned up