Hi Vigz,
If you have a 300GB of RAM machine, you’d want a lower heap size, to leave room
for OS to cache files. Also, the real memory usage of the JVM would likely go
beyond your RAM, in which case either the JVM memory will go to swap (which
would kill performance) or the OS will kill the proc
Hello,
Would it work if you had two facet.query clauses? One with
availabilities:[NOW TO NOW] and one with the same clause negated?
I'm not sure if you need the actual result of the query. If not, maybe it's
simpler to run two queries (one with the clause, one with the clause
negated) and return
Hi Satya,
I didn't try it, but does it work if you add "shards=shard1,shard2..." to
the request?
Worst case scenario, if you have the address of each shard (you can get it
from Zookeeper), you can run the delete command N times, one hitting each
shard address.
Best regards,
Radu
--
Elasticsearch
Hi Nikhilesh,
Try hard-committing more often. This way you'll have smaller tlog files and
there will be less data to recover. My suggestion is to add a maxSize
constraint to autoCommit. 100MB is a good rule of thumb, makes sure you
don't replay more than 100MB worth of data (even if you have an in
gt; Thank you Radu for the quick response. I have updated the values as
> you suggested.
>
>
> Nikhilesh Jannu Principal Software Engineer 405.609.4259
> <(405)%20741-9895>
>
>
> On Wed, Jun 29, 2022 at 12:03 AM Radu Gheorghe >
> wrote:
>
> > Hi
Hi Eugene,
As far as I know, there's no alternative to CDCR within Solr. And yes, it
would be dangerous for the cluster to span multiple DCs. Not so much Solr
itself (you could use shard preference to get queries to hit only one DC),
but for Zookeeper. All Solr(Cloud) nodes will have to keep an op
Nono, I'm sure Java 11 support was there before 8.x came out.
I generally stick to LTS releases (so Java 17 for Solr 9.x and 11 8.x).
Best regards,
Radu
--
Elasticsearch/OpenSearch & Solr Consulting, Production Support & Training
Sematext Cloud - Full Stack Observability
http://sematext.com/
On
; Ta! Paul
>
> Get Outlook for iOS<https://aka.ms/o0ukef>
>
> From: Radu Gheorghe
> Sent: Friday, July 1, 2022 3:49:56 PM
> To: users@solr.apache.org
> Subject: Re: Solr 8.1.1 - OpenJDK 11
>
> Nono, I'm sure Java 11 support wa
lesh Jannu Principal Software Engineer 405.609.4259
> <(405)%20741-9895>
>
>
> On Wed, Jun 29, 2022 at 10:15 PM Radu Gheorghe >
> wrote:
>
> > You're welcome, Nikhilesh!
> >
> > Best wishes,
> > Radu
> > --
> > Elasti
f the recovery is going on. So if the
> recovery is going on should we be make sure there is no traffic sending
> data to be indexed to the collection ?
>
> Regards,
> Nikhilesh Jannu
>
>
>
> Nikhilesh Jannu Principal Software Engineer 405.609.4259
> <(4
Hi Stephen,
I would generally prefer a low value of "maxAtOnce" when calling
REBALANCELEADERS, so that I don't add too much pressure at once. Something
like 1 or 2 should be OK, unless there are other constraints that get in
the way.
I assume that if you have too many at once (and by default, it
Hi Colvin,
You wouldn't normally query with more than e.g. 1K terms at once, because
the query can get expensive.
Here's a crazy idea: map words to numbers, sorted alphabetically. For
example:
aardvark - 1
blip - 2
potato - 3
red - 4
When you formulate the query, you do the same translation, so
Hi Vince,
Here's a tutorial for installing an external ZK + Solr on k8s:
https://sematext.com/blog/solr-operator-autoscaling-tutorial/
Hope it helps.
Radu
--
Elasticsearch/OpenSearch & Solr Consulting, Production Support & Training
Sematext Cloud - Full Stack Observability
https://sematext.com/
13 matches
Mail list logo
