From 1581696f59d132521dff83271b81ee8b371bb6c5 Mon Sep 17 00:00:00 2001 From: Peter Vlugter Date: Thu, 22 Oct 2020 23:37:01 +1300 Subject: [PATCH] Fix typo in docs for cluster sharding rolling updates (#29771) --- akka-docs/src/main/paradox/additional/rolling-updates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/akka-docs/src/main/paradox/additional/rolling-updates.md b/akka-docs/src/main/paradox/additional/rolling-updates.md index 2e9dccf117..fd9847177d 100644 --- a/akka-docs/src/main/paradox/additional/rolling-updates.md +++ b/akka-docs/src/main/paradox/additional/rolling-updates.md @@ -45,8 +45,8 @@ other remaining nodes in the cluster when messages are sent to those shards. To make rolling updates as smooth as possible there is a configuration property that defines the version of the application. This is used by rolling update features to distinguish between old and new nodes. For example, -the default `LeasShardAllocationStrategy` avoids allocating shards to old nodes during a rolling update. -The `LeasShardAllocationStrategy` sees that there is rolling update in progress when there are members with +the default `LeastShardAllocationStrategy` avoids allocating shards to old nodes during a rolling update. +The `LeastShardAllocationStrategy` sees that there is rolling update in progress when there are members with different configured `app-version`. To make use of this feature you need to define the `app-version` and increase it for each rolling update.