Hi, Solr Operator supports v9.x. But currently you'd have to scale the PODs yourself and to add replicas yourself.
There is a recent proposal to make this situation better: https://cwiki.apache.org/confluence/display/SOLR/SIP-17%3A+Node+Autoscaling+via+Kubernetes Jan > 30. mar. 2023 kl. 17:10 skrev Phill Campbell <sirgilli...@yahoo.com.INVALID>: > > From my reading the current solutions depends on Solr Autoscaling and on > Horizontal Pod Autoscaler. > > From Solr docs: > > Deprecations > > The autoscaling framework is now formally deprecated and will be removed in > Solr 9.0. The Solr community is working on pluggable API to replace this > functionality, with the goal for it to be ready by the time 9.0 is released. > Deprecations include: autoscaling policy, triggers, withCollection support, > simulation framework, autoscaling suggestions tab in the UI, autoAddReplicas > and UTILIZENODE command. > > > And from directions on AWS: > > Scaling replicas with SolrCloud autoscaling > SolrCloud (version 8.x) comes with built-in autoscaling feature that allows > replicas to be added or removed automatically from a pod depending on the > metrics being monitored. The deployment uses a collection-level cluster > policy to scale replicas. Cluster policies can also be applied at a shard or > node (pod) level. You can configure SolrCloud autoscaler to track the search > rate event by monitoring the requests per minute value available via the > QUERY./select.requestTimes:1minRatemetric, for scaling the replicas. This > metric is monitored and used to scale the number of replicas in the SolrCloud > cluster. Note that there are a number of other SolrCloud metrics available > via the Solr metrics API that you can consider while defining and fine-tuning > replica autoscaling for the SolrCloud cluster. > > > And it seems that the Solr Operator needs Solr Autoscaling found in v8. > > Is that correct? > > I have an opportunity to re-architect our deployment but I do not want to go > to Solr 9 without K8 (Kubernetes) integration. > > The system is 300 JVMs, 100 shards with replication factor 3. I deploy them > onto EC2 and have in house code to manage the IPs for everything and create > and distribute the replicas across availability zones. Near 1 billion > records, 4K Queriers per Minute, 1.5K upsets per minute that can burst to 6K > upsets per minute for weeks. > > > >> On Mar 29, 2023, at 6:32 PM, Deepak Vohra <dvohr...@yahoo.com.INVALID> wrote: >> >> Apache Solr Operator manages Solr resources in KubernetesDoesn't it support >> version 9 yet?https://solr.apache.org/operator/ >> 8.6+ is listed as supported, which should include 9.2. >> https://apache.github.io/solr-operator/docs/upgrade-notes.html >> >> On Wednesday, March 29, 2023 at 04:29:25 p.m. EDT, Phill Campbell >> <sirgilli...@yahoo.com.invalid> wrote: >> >> I have been looking for an example of how to use Solr 9 with Kubernetes. >> All of the examples I have found are using Solr 8 and Solr 8’s autoscaling. >> >> Since autoscaling is deprecated in Solr 9 I was hoping to find guidance for >> Solr 9. >> >> >
