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

Extra warning about rolling upgrades and sharding added (#23000)

Browse source 
* Extra warning about rolling upgrades and sharding added

* More clear
This commit is contained in:
Johan Andrén 2017-05-23 15:47:05 +02:00 • committed by Patrik Nordwall
parent 5c92071441
commit 7f12bd9f4e
2 changed files with 21 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

12
akka-docs/src/main/paradox/java/cluster-sharding.md
View file

@ -213,7 +213,7 @@ the cluster have been stopped the state is lost and not needed any more.
The state of [Remembering Entities](#cluster-sharding-remembering) is also durable, i.e. it is stored to The state of [Remembering Entities](#cluster-sharding-remembering) is also durable, i.e. it is stored to
disk. The stored entities are started also after a complete cluster restart. disk. The stored entities are started also after a complete cluster restart.
Cluster Sharding is using its own Distributed Data `Replicator` per node role. In this way you can use a subset of Cluster Sharding is using its own Distributed Data `Replicator` per node role. In this way you can use a subset of
all nodes for some entity types and another subset for other entity types. Each such replicator has a name all nodes for some entity types and another subset for other entity types. Each such replicator has a name
that contains the node role and therefore the role configuration must be the same on all nodes in the that contains the node role and therefore the role configuration must be the same on all nodes in the
cluster, i.e. you can't change the roles when performing a rolling upgrade. cluster, i.e. you can't change the roles when performing a rolling upgrade.
@ -423,3 +423,13 @@ of entities that are alive in each shard.
The purpose of these messages is testing and monitoring, they are not provided to give access to The purpose of these messages is testing and monitoring, they are not provided to give access to
directly sending messages to the individual entities. directly sending messages to the individual entities.
## Rolling upgrades
When doing rolling upgrades special care must be taken to not change any of the following aspects of sharding:
* the `extractShardId` function
* the role that the shard regions run on
* the persistence mode
If any one of these needs a change it will require a full cluster restart.

10
akka-docs/src/main/paradox/scala/cluster-sharding.md
View file

@ -425,3 +425,13 @@ of entities that are alive in each shard.
The purpose of these messages is testing and monitoring, they are not provided to give access to The purpose of these messages is testing and monitoring, they are not provided to give access to
directly sending messages to the individual entities. directly sending messages to the individual entities.
## Rolling upgrades
When doing rolling upgrades special care must be taken to not change any of the following aspects of sharding:
* the `extractShardId` function
* the role that the shard regions run on
* the persistence mode
If any one of these needs a change it will require a full cluster restart.