These are chat archives for akkadotnet/akka.net
Cheap flights tickets from London to Paris Last minute hotels and car rentals in east London Uk
Start your adventure with cheap flight tickets from London to Paris and do not get the tired book last minute hotels in the UK , for ride book cheap car rentals in east London. Take advantage of the huge range of budget carriers including EasyJet, Ryanair, Jet2 and BMI Baby to luxury airlines like Emirates and lesser known operators cheap flight tickets from London to Paris.
cheap flight tickets from london to paris, last minute hotels in uk, cheap car rentals in east London
@Horusiath I have used cluster sharding and it seems it is just what I was looking for. But I have a problem with it. When I start a few nodes (lets say 3) Akka distributes state among shards perfectly. But when I kill some node everything crashes and I am receiving these logs from on all other nodes:
16:15:26.219 [Debug] [ShardRegion [[akka.tcp://Q@localhost:58877/system/sharding/PersistentChatActor#1039458924]] was not registered since the coordinator currently does not know about a node of that region] |
How to make my cluster to rebalance and move the state from the dead node and distribute it among alive nodes?
@ondrejpialek why do you think that system-wide crash would break cluster sharding?
Ah sorry, poor wording on my part. I meant to say that the auto-start feature does not kick in on system start following a system crash, it only recreates them on shard migration (I actually don't know if this is true, my understanding is based on the docs). I was specifically replying to:
When my system crashes, I would like to restore it to the previous state which includes recreating all the ongoing chat conversations.
For that some external state handling is needed to keep track of active conversations, either by the means of Persistent manager or a projection.
sharding.remember-entities = trueAkka provides children restoration out of the box.
akka.cluster.auto-down-unreachable-after = 10s- it will mean that any node, that was unreachable for more than 10 seconds, will be automatically marked as dead