-
Notifications
You must be signed in to change notification settings - Fork 114
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
Create Collection fails after Upgrade #627
Comments
the upgrade strategy used was Managed (which delegates the upgrades to operator) |
Could you provide the Solr logs? The operator wouldn't be preventing the collection from being created, so it has to be something on the Solr side. |
lot of logs. copying the just around the time frame i hit the create api
|
do I have to call Rebalance API on each solrcloud node ? |
scaled down the cluster to 2 node... it removed solrcloud-2 and did autoscalling back to 3. After it brought back solrcloud-2 node, this issue went away. the root cause of original issue seems to be a TIMEOUT issue in solrcloud-1 and solrcloud-2 unable to reach ( or intermittent??) to solrcloud-0 . After the scaling activity... things were back to normal. Still fingers crossed with the UPGRADE process. will test again. closing ticket for now. |
Setup:
K8S cluster: AWS EKS 1.27
Solr Operator : 0.7.1 helm chart
Solr cloud version: 9.3
ZK : inbuilt w/operator
Nodes: 3 solr nodes ( pod solrcloud-0, solrcloud-1, solrcloud-2)
Cluster has been operational with a stanard collection setup of 1 shard : 3 replica .
Data was distributed evenly across solr nodes and solrcloud-0 being the leader.
Performed an upgrade via "helm upgrade solr apache-solr/solr --version 0.7.1 --reuse-values --set image.tag=xx"
This caused solrcloud-1 upgrade n recycled , followed by solrcloud-2 pod and followed by solrcloud-0 pod.
By the time solrcloud-0 pod came up , the data was distributed within other 2 pods.
After the upgrade, attempting to CREATE collection via curl v2 api endpoint.
The collection create request timed out. Able to see the collection "grocery" in the Graph and that collection never comes up and gets "auto-cleaned" (collection disappears after a while)
See image ... grocery is the collection created after the upgrade . Other 2 existed before the upgrade.
The text was updated successfully, but these errors were encountered: