raboof/pekko
1
0
Fork 0
Code Issues Pull requests Projects Releases 6 Packages Wiki Activity Actions 11

Document rolling upgrades of clusters using ddata (#23372)

Browse source
This commit is contained in:
Arnout Engelen 2017-08-16 04:54:10 -07:00 • committed by GitHub
parent c1f247212f
commit 4f0ff3ac13
1 changed files with 8 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

13
akka-docs/src/main/paradox/scala/project/migration-guide-2.4.x-2.5.x.md
View file

@ -416,10 +416,10 @@ Some settings have changed default value in 2.5-M1 and therefore you need to rev
before doing a rolling update to 2.5-M1. Such settings are mentioned elsewhere in this migration guide before doing a rolling update to 2.5-M1. Such settings are mentioned elsewhere in this migration guide
and here is a summary of things to consider. and here is a summary of things to consider.
* [additional-serialization-bindings](#mig25-addser) * [akka.actor.additional-serialization-bindings](#mig25-addser)
* [WeaklyUp](#mig25-weaklyup) * [akka.cluster.allow-weakly-up-members](#mig25-weaklyup)
* [Cluster Sharding state-store-mode](#mig25-sharding-store) * [akka.cluster.sharding.state-store-mode](#mig25-sharding-store)
* [Mutual TLS authentication](#mig25-mutual) * [akka.remote.netty.ssl.require-mutual-authentication](#mig25-mutual)
#### Limit lookup of routees to nodes tagged with multiple roles #### Limit lookup of routees to nodes tagged with multiple roles
@ -472,7 +472,7 @@ you might need to enable/disable it in configuration when performing rolling upg
<a id="mig25-sharding-store"></a> <a id="mig25-sharding-store"></a>
### Cluster Sharding state-store-mode ### Cluster Sharding state-store-mode
Distributed Data mode is now the default `state-store-mode` for Cluster Sharding. The persistence mode Distributed Data mode, which was still experimental in 2.4.x, is now the default `state-store-mode` for Cluster Sharding. The persistence mode
is also supported. Read more in the @ref:[documentation](../cluster-sharding.md#cluster-sharding-mode). is also supported. Read more in the @ref:[documentation](../cluster-sharding.md#cluster-sharding-mode).
It's important to use the same mode on all nodes in the cluster, i.e. if you perform a rolling upgrade It's important to use the same mode on all nodes in the cluster, i.e. if you perform a rolling upgrade
@ -487,6 +487,9 @@ Note that the stored @ref:[Remembering Entities](../cluster-sharding.md#cluster-
be migrated to the `data` mode. Such entities must be started again in some other way when using be migrated to the `data` mode. Such entities must be started again in some other way when using
`ddata` mode. `ddata` mode.
Rolling upgrades from clusters that already used the (then-experimental) `ddata`
mode are not supported.
### Cluster Sharding remember entities ### Cluster Sharding remember entities
To use *remember entities* with cluster sharding there are now an additional requirement added: the To use *remember entities* with cluster sharding there are now an additional requirement added: the