So the SIP for this is
https://cwiki.apache.org/confluence/display/SOLR/SIP-17%3A+Node+Autoscaling+via+Kubernetes,
and you can find more information there.
The features are not released, but they should be available starting with
Solr 9.3 and the Solr Operator v0.8.0.
As for adding new replicas
>
> > Hello Solr (operator) community!
> >
> > As far as I understood from the jira
> >
> >
> https://cwiki.apache.org/confluence/display/SOLR/SIP-17%3A+Node+Autoscaling+via+Kubernetes
> > , this is quite a lot of work ongoing since the AutoScaling
> > funct
gt; Hello Solr (operator) community!
>
> As far as I understood from the jira
>
> https://cwiki.apache.org/confluence/display/SOLR/SIP-17%3A+Node+Autoscaling+via+Kubernetes
> , this is quite a lot of work ongoing since the AutoScaling
> functionality in Solr has been deprecated. How
Hello Solr (operator) community!
As far as I understood from the jira
https://cwiki.apache.org/confluence/display/SOLR/SIP-17%3A+Node+Autoscaling+via+Kubernetes
, this is quite a lot of work ongoing since the AutoScaling
functionality in Solr has been deprecated. However, it is not clear to me
if
ks in advance,
> Adi
>
> -Original Message-
> From: Shawn Heisey
> Sent: Monday, July 18, 2022 12:42 AM
> To: users@solr.apache.org
> Subject: Re: Autoscaling
>
> On 7/17/22 11:25, Kaminski, Adi wrote:
>> For example, if we have 10 shards each 100k (1M total)
hear some direction.
Thanks in advance,
Adi
-Original Message-
From: Shawn Heisey
Sent: Monday, July 18, 2022 12:42 AM
To: users@solr.apache.org
Subject: Re: Autoscaling
On 7/17/22 11:25, Kaminski, Adi wrote:
> For example, if we have 10 shards each 100k (1M total) documents size fo
On 7/17/22 11:25, Kaminski, Adi wrote:
For example, if we have 10 shards each 100k (1M total) documents size for best
and optimized ingestion/query performance...adding more documents will make
sense to have 11th shard, and reaching 1.1M total will make sense to add 12th
one eventually.
One
ization (per volume, date, any other custom logic..).
>
> Thanks in advance,
> Adi
>
>
> Get Outlook for Android<https://aka.ms/AAb9ysg>
>
> From: Shawn Heisey
> Sent: Sunday, July 17, 2022 5:44:24 PM
> To: users@solr.apach
other custom logic..).
Thanks in advance,
Adi
Get Outlook for Android<https://aka.ms/AAb9ysg>
From: Shawn Heisey
Sent: Sunday, July 17, 2022 5:44:24 PM
To: users@solr.apache.org
Subject: Re: Autoscaling
On 7/17/22 07:40, Ronen Nussbaum wrote:
> We a
On 2022-07-17 11:37 AM, Dave wrote:
...
Containers are great for developing and fast deployment but I would never put
one in front of live users. Maybe it’s a trust issue? But I like metal
Bare metal is great when you have your own datacenter. When you don't
have the money to build one from s
>>> It is already deployed as Docker containers.
>>>> Instead of estimating in advance what is the number of shards needed, or
>>>> the number of pods, we'd like to rely on EKS cluster autoscaler, K8S HPA
>>>> and Solr autoscaling.
>>>> Our m
o the cloud.
>>> Currently it is installed on-prem for each customer.
>>> It is already deployed as Docker containers.
>>> Instead of estimating in advance what is the number of shards needed, or
>>> the number of pods, we'd like to rely on EKS cluster autosc
he number of pods, we'd like to rely on EKS cluster autoscaler, K8S HPA
>> and Solr autoscaling.
>> Our main concern is the deprecation of the autoscaling feature since
>> version 9.0.
>
> One thing I am not sure you're aware of: You can't add shards to
, we'd like to rely on EKS cluster autoscaler, K8S HPA
and Solr autoscaling.
Our main concern is the deprecation of the autoscaling feature since
version 9.0.
One thing I am not sure you're aware of: You can't add shards to a
collection unless it is using the implicit router, which
uster autoscaler, K8S HPA
and Solr autoscaling.
Our main concern is the deprecation of the autoscaling feature since
version 9.0.
What is your recommendation? Should we start with 8.11? Will it be a
substitute soon?
I'd appreciate any feedback.
Thank you in advance,
Ronen.
15 matches
Mail list logo
