added Akka.NET v1.3.3 release notes [dev] #3280
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1.3.3 January 19 2019
Maintenance Release for Akka.NET 1.3
The largest changes featured in Akka.NET v1.3.3 are the introduction of Splint brain resolvers and
WeaklyUpmembers in Akka.Cluster.Akka.Cluster Split Brain Resolvers
Split brain resolvers are specialized
IDowningProviderimplementations that give Akka.Cluster users the ability to automatically downUnreachablecluster nodes in accordance with well-defined partition resolution strategies, namely:You can learn more about why you may want to use these and which strategy is right for you by reading our Splint brain resolver documentation.
Akka.Cluster
WeaklyUpMembersOne common problem that occurs in Akka.Cluster is that once a current member of the cluster becomes
Unreachable, the leader of the cluster isn't able to allow any new members of the cluster to join until thatUnreachablemember becomesReachableagain or is removed from the cluster via aCluster.Downcommand.Beginning in Akka.NET 1.3.3, you can allow nodes to still join and participate in the cluster even while other member nodes are unreachable by opting into the
WeaklyUpstatus for members. You can do this by setting the following in your HOCON configuration beginning in Akka.NET v1.3.3:This will allow nodes who have joined the cluster when at least one other member was unreachable to become functioning cluster members with a status of
WeaklyUp. If the unreachable members of the cluster are downed or become reachable again, allWeaklyUpnodes will be upgraded to the usualUpstatus for available cluster members.Akka.Cluster.Sharding and Akka.Cluster.DistributedData Integration
A new experimental feature we've added in Akka.NET v1.3.3 is the ability to fully decouple Akka.Cluster.Sharding from Akka.Persistence and instead run it on top of Akka.Cluster.DistributedData, our library for creating eventually consistent replicated data structures on top of Akka.Cluster.
Beginning in Akka.NET 1.3.3, you can set the following HOCON configuration option to have the
ShardingCoordinatorreplicate its shard placement state using DData instead of persisting it to storage via Akka.Persistence:This setting only affects how Akka.Cluster.Sharding's internal state is managed. If you're using Akka.Persistence with your own entity actors inside Akka.Cluster.Sharding, this change will have no impact on them.
Updates and bugfixes:
Cluster.JoinAsyncandClutser.JoinSeedNodesAsyncmethodsYou can see the full changeset for Akka.NET 1.3.3 here.