-
Notifications
You must be signed in to change notification settings - Fork 118
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
Getting unauthorized requests for cluster/replicas/balance in v0.8.0 #653
Comments
Not sure, but could be a similar/related issue.
Same error on Solr side:
why is the operator hitting this path? Thanks for any help. |
@mmoscher , that is expected. After the completion of an ephemeral rolling restart, the Solr Operator now tries to balance the cluster. If Solr doesn't support that command (and 9.0 does not), it just completes the operation. But the only way that the Solr Operator can know if it's supported is to try running it. @ozlerhakan I think that is something that we missed. I'll try to add a PR for that soon. |
Is there a workaround for this? We're getting the same error after starting up a brand new cluster. |
As a workaround, you can manually add However just a warning that rebalancing doesn't seem to work very well so you may just want to leave it off... it seems to just create a whole bunch of replicas then time out, then leaves a bunch of replicas on the new nodes without deleting the ones on the old node. After failing, it runs rebalance again, then instantly declares it was a "success" even though the replicas never got moved properly and now you have more replicas than you started with.
|
Hi Team,
We've recently changed the operator version from v0.7.0 to v0.8.0 for our SolrCloud cluster (9.4).
It seems that the new version requests the status of an async task named
balance-replicas-ScaleUp
every 60 seconds. Once it doesn't find one running, it sends a "replica/balance" request to the target Solr, therefore we're getting the following error for every attempt:I found that the relevant metadata for this use case is written into the annotation field of the statefulsets object:
"solr.apache.org/clusterOpsLock": "{\"operation\":\"BalanceReplicas\",\"lastStartTime\":\"2023-11-09T14:28:18Z\",\"metadata\":\"ScaleUp\"}"
We're using the default security.json credentials and I'm not certain if there's anything to be changed in our settings for this matter.
Thanks!
The text was updated successfully, but these errors were encountered: