This is an automated email from the ASF dual-hosted git repository.
mkhl pushed a commit to branch branch_9x
in repository https://gitbox.apache.org/repos/asf/solr.git
The following commit(s) were added to refs/heads/branch_9x by this push:
new 734920a3c2d Update replica-placement-plugins.adoc (#2155) (#2156)
734920a3c2d is described below
commit 734920a3c2dd40c889b06930187eb844062ea9b7
Author: Mikhail Khludnev <[email protected]>
AuthorDate: Fri Dec 15 12:17:42 2023 +0300
Update replica-placement-plugins.adoc (#2155) (#2156)
Co-authored-by: mariemat <[email protected]>
---
.../modules/configuration-guide/pages/replica-placement-plugins.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/solr/solr-ref-guide/modules/configuration-guide/pages/replica-placement-plugins.adoc
b/solr/solr-ref-guide/modules/configuration-guide/pages/replica-placement-plugins.adoc
index 0ce84efaf68..6cf06903014 100644
---
a/solr/solr-ref-guide/modules/configuration-guide/pages/replica-placement-plugins.adoc
+++
b/solr/solr-ref-guide/modules/configuration-guide/pages/replica-placement-plugins.adoc
@@ -133,7 +133,7 @@ If `withCollection` or `withCollectionShards` are defined
and applicable to the
** Iterate over the number of replicas to place (for the current replica type
for the current shard):
*** Based on the number of replicas per AZ collected previously, pick the
non-empty set of nodes having the lowest number of replicas.
Then pick the first node in that set.
-That's the node the replica is placed one.
+That's the node the replica is placed on.
Remove the node from the set of available nodes for the given AZ and increase
the number of replicas placed on that AZ.
** During this process, the number of cores on the nodes in general is tracked
to take into account placement decisions so that not all shards decide to put
their replicas on the same nodes (they might though if these are the less
loaded nodes).
