forked from akkadotnet/akka.net
-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Batch update with singleton/sharding fixes (akkadotnet#3780)
* Introduce 'MemberDowned' member event Migrated from #25854 * Ignore possible state change while waiting for removal Migrated from #25274 * mark TryToIdentifySingleton as NoSerializationVerificationNeeded Migrated from #24442 * Improvements of singleton leaving scenario Migrated from #25639 (#25710) Testing of singleton leaving gossip optimization, exiting change to two oldest per role hardening ClusterSingletonManagerIsStuck restart, increase ClusterSingletonManagerIsStuck * Stop singleton and shards when self MemberDowned Migrated from #26336 (#26339) Stop singleton when self MemberDowned * It's safer to stop singleton instance early in case of downing. * Instead of waiting for MemberRemoved and trying to hand over. Stop ShardRegion when self MemberDowned Upper bound when waiting for seen in shutdownSelfWhenDown * Discards HandOverToMe in state End to avoid unhandled message warning Migrated from #26793 * Warn if handOffStopMessage not handled Migrated from #25648 Stops entities of shard forcefully if they don't handle stopMessage Prints a warning log while stopping the entities fix version of backward exclude file and checks for shard stopped adds documentation for handoff timeout * Save EntityStarted when StartEntity requested via remembered entities (for validation) Migrated from #26061 * Improve default shard rebalancing algorithm Migrated from #26012 (#26101) * Improve default shard rebalancing algorithm * Use rebalance-threshold=1 because it will give the best distribution, and previous default could result in too large difference between nodes * Off by one error, difference > threshold vs >= * Added more unit tests * Note that in some cases it may still not be optimal, stopping more shards than necessary, but a different strategy that looks at more than most and least is out of scope for this issue. In practise those cases shouldn't matter much. * Also note that the rebalance interval is by default 10 seconds, so typically shards will start up before next rebalance tick. It's intentionally a slow process to not cause instabilities by moving too much at the same time. * Always retry sendGracefulShutdownToCoordinator Migrated from #26214 * I could reproduce the issue locally with debug logging and it's clear that it's a timing issue. The GracefulShutdownReq message goes to deadletters and it's not retried because the coordinator variable was unset. * cluster-sharding-shutdown-region phase of CoordinatedShutdown timed out * Consolidate duplicate persistence sharding function Migrated from #26451 (#26452) * API approval * sharding with ddata specs timing issue fix * Enable passivate-idle-entity-after by default Migrated from #25782 (#26819) * persistent shard passivate-idle fix ddata passivate-idle fix sharding fixes (part of #26878) * Removed references to System.ValueTuple
- Loading branch information
1 parent
e96d567
commit 125d738
Showing
35 changed files
with
1,148 additions
and
258 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.