Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:56
    Aaronontheweb synchronize #4128
  • 16:46

    Aaronontheweb on explain-sharding-path

    (compare)

  • 16:46

    Aaronontheweb on dev

    Update cluster-sharding.md (#41… (compare)

  • 16:46
    Aaronontheweb closed #4164
  • 16:46
    Aaronontheweb closed #4161
  • 16:44
    Aaronontheweb opened #4164
  • 16:43

    Aaronontheweb on explain-sharding-path

    Update cluster-sharding.md (compare)

  • 16:38
    Aaronontheweb assigned #4161
  • 16:38
    Aaronontheweb labeled #4161
  • 16:38
    Aaronontheweb commented #4161
  • 16:37
    Aaronontheweb unlabeled #4078
  • 16:37
    Aaronontheweb closed #4078
  • 16:37
    Aaronontheweb commented #4078
  • 16:01
    Aaronontheweb commented #4126
  • 16:00
    Aaronontheweb synchronize #4126
  • 15:54

    Aaronontheweb on dev

    Add inner exceptions to spec fa… (compare)

  • 15:54
    Aaronontheweb closed #4163
  • 15:54
    Aaronontheweb closed #4162
  • 15:54
    Aaronontheweb labeled #4162
  • 15:54
    Aaronontheweb labeled #4162
Just calling var resolver = new SimpleInjectorDependencyResolver(container, system); is enough
it registers itself with the system
the system.AddDepedencyResolver is a public api exposed for the DI plugins to use. It should not be used directly. Although it is possible, if you know what you are doing.
Peter Hvidgaard
@hvidgaard
@Danthar Alright, removed that line, but the example still fails because SI creates all registered dependencies during verification.
Arjen Smits
@Danthar
@riawz ExpectMsgAllOf ??
Oh? thats odd.
riawz
@riawz
actually, I don't need it, I have actor A which creates actor B, B is roundrobin, but when I'm testing, I can only test against a single instance of actor B, so I don't need it, thanks
A will receive 2 response from 2 B instances, that's what I was thinking of testing but I can't find a way to "mock" router using testkit
Arjen Smits
@Danthar
@hvidgaard it looks like the SimpleInjector plugin is still on 1.0.8 ?
The tests work. So plugin integration for 1.0.8 looks good
Peter Hvidgaard
@hvidgaard
I've updated to the latest akka.net packages, I assumed that a minor version increase wasn't a problem.
Arjen Smits
@Danthar
Have you ran the tests ?
Peter Hvidgaard
@hvidgaard
no, I've used the NuGet packages.
Arjen Smits
@Danthar
That would be a problem :P
If you upgrade, you should rebuild the plugin against the latest akka.net packages
Peter Hvidgaard
@hvidgaard
okay, good to know...
Arjen Smits
@Danthar
I just forked the repo and got the env open just now. ill check for you
It looks ok.
I gtg, got a meeting
Peter Hvidgaard
@hvidgaard
alright, playing with it myself. Thanks so far
Arjen Smits
@Danthar
but if you update the repo to have the plugin use the latest akka.net. And build a version explicitly targetting it, that should work
also check the tests project of the plugin, for details on how to register dependencies
could be the readme is wrong
Peter Hvidgaard
@hvidgaard
ok, I'll try that.
Arjen Smits
@Danthar
gl!
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 :)