Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 16:43
    dependabot-preview[bot] edited #4276
  • 16:42
    Aaronontheweb commented #4276
  • 16:31
    Aaronontheweb closed #4273
  • 16:31
    Aaronontheweb commented #4273
  • 16:27

    dependabot-preview[bot] on nuget

    (compare)

  • 16:27
    dependabot-preview[bot] closed #4274
  • 16:27
    dependabot-preview[bot] commented #4274
  • 16:27
    dependabot-preview[bot] labeled #4276
  • 16:27
    dependabot-preview[bot] opened #4276
  • 16:27

    dependabot-preview[bot] on nuget

    Bump Hocon.Configuration from 2… (compare)

  • 16:24
    Aaronontheweb labeled #4275
  • 16:24
    Aaronontheweb labeled #4275
  • 16:24
    Aaronontheweb opened #4275
  • 16:24
    Aaronontheweb milestoned #4275
  • 06:45

    dependabot-preview[bot] on nuget

    Bump Hocon.Configuration from 2… (compare)

  • 06:45
    dependabot-preview[bot] labeled #4274
  • 06:45
    dependabot-preview[bot] opened #4274
  • 04:01
    Aaronontheweb synchronize #4270
  • 04:00

    Aaronontheweb on dev

    ClusterRouter no routees on sta… (compare)

  • 04:00
    Aaronontheweb closed #4272
Bartosz Sypytkowski
@Horusiath
@easysoft2k15 @llehn Akka.Cluster.Sharding is plugin designed to work on actors as aggregate roots, created on demand, migrated, routed and rebalanced across cluster nodes.
Alessandro Rizzotto
@easysoft2k15
@Horusiath I'll dig deeper in the sharding cluster doc. At the moment (keeping everything on a single machine) I'm adopting the solution I explained above.
Chris Martin
@trbngr
I'm trying to use Cluster.Sharding with lighthouse but my shards aren't being resolved. Please tell me I can use Lighthouse as just a dumb seed.
and not have to launch the region there too
Bartosz Sypytkowski
@Horusiath
@trbngr you may need to specify roles for sharding nodes (I'm not 100% sure if it's necessary) and use them in sharding config
Chris Martin
@trbngr
ok. I'll give it a shot
Bartosz Sypytkowski
@Horusiath
because cluster sharding may assume, that lighthouse will also host shards
Chris Martin
@trbngr
            cluster {
              sharding {
                role = "projections"
              }
              #will inject this node as a self-seed node at run-time
              seed-nodes = [
                "akka.tcp://eventdayprojections@168.62.228.228:4053",
                "akka.tcp://eventdayprojections@23.96.183.175:4053"
              ]
              roles = [projections]
            }
          }
look right?
Bartosz Sypytkowski
@Horusiath
yes
Chris Martin
@trbngr
still not happening :(
Bartosz Sypytkowski
@Horusiath
any errors?
Chris Martin
@trbngr
Trying to register to coordinator at [], but no acknowledgement. Total [1] buffered messages.
oh! I don't have any journal setup
sorry. I've been in Scala-land for the last few months. Trying to get my head back here for a bit ;)
hmm. defaults to inmem, right?
Bartosz Sypytkowski
@Horusiath
yes, it won't work right between processes
Chris Martin
@trbngr
right right
what can I use without setting anything up?
leveldb?
Bartosz Sypytkowski
@Horusiath
sqlite (if all akka processes will point to the same file)
Chris Martin
@trbngr
hmm. so far this is only one instance. It should work.
wire serializer is also advised (I know, that existing json-based may have some problems with some of the cluster sharding message)
Chris Martin
@trbngr
Oh yes. I remember that
Chris Martin
@trbngr
hmm. the db isn't being created. Seems like the persistence module isn't initializing at all
updated gist if you have time to look
wondering if having my seeds over the internet is the problem at this point?
Bartosz Sypytkowski
@Horusiath
if db is not created, you should have some error messages
could you put logs on the gist?
Chris Martin
@trbngr
I got it working after starting lighthouse locally.
Big question here is what happens when a node goes down? Do the shards get recreated on another node?
Bartosz Sypytkowski
@Horusiath
yes - basically shards can be handed over to another node, or rebalanced when the difference in number of shards between nodes goes over some specified threshold
Chris Martin
@trbngr
seems to hold true ;)
but only if auto-down is set. Well.. I can't tell for sure. Too many logs to see if my messages are received.
Bartosz Sypytkowski
@Horusiath
I know, that @Aaronontheweb often says to be careful with auto-down, but to be honest - unless you'll specify your own logic for downing nodes, I think it's a reasonable to use it (at least for clusters, which fit into single datacenter).
Chris Martin
@trbngr
I think that's reasonable too. It's always in the back of my mind though. The Akka guys warn against that hard.
I suppose it's not a huge deal with a small system either
Bartosz Sypytkowski
@Horusiath
in akka on the jvm you can use split-brain resolver strategies, we don't have them on .net side yet
Chris Martin
@trbngr
ok. thanks for your help, man. Ima go code now
Aaron Stannard
@Aaronontheweb
where auto-down kicks you in the nuts is when the unexpected happens
if there's a hardware failure inside azure that knocks out the network for a minute or two
then you have to take your service offline and do a full reboot if every node has downed every other node
it's a remote possibility though
and most businesses that couldn't tolerate that issue
wouldn't tolerate that type of outage in the first place
and would have some sort of data-center level failover
it'll be useful once we have downing providers implemented
makes the strategy for doing automatic downing pluggable
Chris Ochs
@gamemachine
wanted to confirm behavior on singleton actor. That it's being unreachable that triggers moving it, it doesn't have to be flagged as down before it moves