Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replica allocation after Node is DisabledScheduling #703

Open
brickpattern opened this issue May 9, 2024 · 1 comment
Open

Replica allocation after Node is DisabledScheduling #703

brickpattern opened this issue May 9, 2024 · 1 comment

Comments

@brickpattern
Copy link

brickpattern commented May 9, 2024

Q - Similar to Kubectl Cordon that disables a pod scheduling on that node, is there equivalent of that for the Solr Operator?

  1. The solrcloud-n pod is already active and alloted with certain core/replica on it. How to prevent further core/replica allocation on that pod?
  2. when hitting SPLITSHARD via api, how to prevent that core/replica from going into solrcloud-n pod.
  3. when solr core/replica was filling up , had to manually Rebalance by hitting REBALANCEAPI . should operator be automatically moving the core/replica to another available pod?
@HoustonPutman
Copy link
Contributor

This is something that would also have to be implemented in Solr, not just the Solr Operator, because there is no mechanism currently to "cordon-off" nodes when placing replicas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants