brickpattern opened a new issue, #627: URL: https://github.com/apache/solr-operator/issues/627
Setup: K8S cluster: AWS EKS 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. <img width="998" alt="image" src="https://github.com/apache/solr-operator/assets/9627703/17dfc5f9-3d26-4727-8e8f-64c2d1403778";> -- 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: issues-unsubscr...@solr.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org For additional commands, e-mail: issues-h...@solr.apache.org
