Fix typo in docs for cluster sharding rolling updates (#29771)

This commit is contained in:
Peter Vlugter 2020-10-22 23:37:01 +13:00 committed by GitHub
parent a023821f8e
commit 1581696f59
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -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 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, 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 default `LeastShardAllocationStrategy` 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 `LeastShardAllocationStrategy` sees that there is rolling update in progress when there are members with
different configured `app-version`. different configured `app-version`.
To make use of this feature you need to define the `app-version` and increase it for each rolling update. To make use of this feature you need to define the `app-version` and increase it for each rolling update.