janhoy commented on issue #788:
URL: https://github.com/apache/solr-operator/issues/788#issuecomment-6478260466
Answering the three parts:
**Replica count** is already preserved — `/api/cluster/replicas/balance`
*moves* replicas between nodes, it never creates them, so a collection has the
same number of replicas before and after a scale-up.
**Avoiding the movement** is the documented toggle. Both
`populatePodsOnScaleUp` and `vacatePodsOnScaleDown` default to `true`, so set
them to `false` if you manage placement yourself:
```yaml
spec:
scaling:
populatePodsOnScaleUp: false
vacatePodsOnScaleDown: false
```
**Constraining `Nodes` to the newly added nodes** wouldn't give you what you
want: that parameter restricts which nodes Solr balances *among*, so passing
only the new (empty) nodes would balance them against each other and move
nothing onto them from the existing pods. Cluster-wide is what makes populating
a new pod work at all.
So the control you're after is `populatePodsOnScaleUp: false`. See
https://solr.apache.org/guide/operator/latest/solr-cloud/scaling.html — closing
as answered, happy to reopen if balancing moves more than you'd expect with
that set.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
